Re: 5.2-BETA: giving up on 4 buffers (ata)
Matthias Andree wrote: > when I rebooted my 5.2-BETA (kernel about 24 hours old), it gave up on > flushing 4 dirty blocks. This is easy to reproduce, but apparently uninteresting to the developers: Reboot to single user, run full fsck, halt. -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
systat drive list
Low priority, but easy to accomplish: Now that my eisa scsi disk controllers are working again, I'd like to monitor the 8 drives attached with systat(1), except its broken. Would someone like to commit this trivial patch? (see pr bin/59220) > cd /usr/src/usr.bin/systat/ > ident devs.c devs.c: $FreeBSD: src/usr.bin/systat/devs.c,v 1.9 2003/10/20 20:13:50 phk Exp $ > diff -u devs.c-orig devs.c --- devs.c-orig Fri Nov 21 13:23:33 2003 +++ devs.c Fri Nov 21 13:46:14 2003 @@ -280,12 +280,12 @@ ; if (*cp) *cp++ = '\0'; - if (cp - args == 0) + if (cp - tmpstr1 == 0) break; for (i = 0; i < num_devices; i++) { asprintf(&buffer, "%s%d", dev_select[i].device_name, dev_select[i].unit_number); - if (strcmp(buffer, tmpstr1) == 0) { + if (strcmp(tmpstr1, buffer) == 0) { num_devices_specified++; @@ -303,8 +303,8 @@ free(buffer); } if (i >= num_devices) - error("%s: unknown drive", args); - args = cp; + error("%s: unknown drive", tmpstr1); + tmpstr1 = cp; } free(tmpstr); -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5-CURRENT totally broken on AMD64 in 32-bit mode
On Tue, 18 Nov 2003, Andy Farkas wrote: > The changes that break things were made more than a week ago. I sent this > email last week: > > > Date: Sun, 9 Nov 2003 09:22:17 +1000 (EST) > > From: Andy Farkas <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Subject: kernel halts before booting > > > > My kernels now break into the debugger before booting! > > > > Boot sequence goes like this: > > > > ... > > Hit [Enter] to boot immediately, or any other key for command prompt. > > Booting [/boot/kernel/kernel]... > > cpuid = 0; apic id = 00 > > instruction pointer = 0x0:0xa00 > > stack pointer = 0x0:0xffe > > frame pointer = 0x0:0x0 > > code segment= base 0x0, limit 0x0, type 0x0 > > = DPL 0, pres 0, def32 0, gran 0 > > processor eflags= interrupt enabled, vm86, IOPL = 0 > > current process = 0 () > > kernel: type 30 trap, code=0 > > stopped at 0xa00: cli > > db> This too has been fixed. Extra cookies for all involved! -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: EISA Adaptec 274X SCSI panic (ISRng related)
On Tue, 18 Nov 2003, Nate Lawson wrote: > On Tue, 18 Nov 2003, Andy Farkas wrote: > > My EISA AHA2740's don't work no more :( > > > > # grep ahc /var/run/dmesg.boot > > ahc0: at 0x2c00-0x2cff, irq 10 (level) > > ahc0: on eisa0 slot 2 > > ahc1: at 0x4c00-0x4cff, irq 11 (level) > > ahc1: on eisa0 slot 4 > > ahc2: port 0xf800-0xf8ff mem > > 0xf68fb000-0xf68fbfff irq 17 at device 11.0 on pci1 > > ahc2: Using left over BIOS settings > > ahc3: port 0xf400-0xf4ff mem > > 0xf68fa000-0xf68fafff irq 18 at device 12.0 on pci1 > > ahc3: Using left over BIOS settings > > > > Fatal trap 12: page fault while in kernel mode > > cpuid = 0; apic id = 00 > > fault virtual address = 0x0 > > fault code = supervisor write, page not present > > instruction pointer = 0x8:0xc0649083 > > stack pointer = 0x10:0xd763ac5c > > frame pointer = 0x10:0xd763ac84 > > code segment= base 0x0, limit 0xf, type 0x1b > > = DPL 0, pres 1, def32 1, gran 1 > > processor eflags= resume, IOPL = 0 > > current process = 14 (idle: cpu0) > > kernel: type 12 trap, code=0 > > Stopped at intr_execute_handlers+0x23: lock addl %eax,0(%edx) > > db> tr > > intr_execute_handlers(c06d5084,d763ac9c,d763ace0,c065bbae,7) at > > intr_execute_handlers+0x23 > > atpic_handle_intr(7) at atpic_handle_intr+0x42 > > Xatpic_intr7() at Xatpic_intr7+0x1e > > --- interrupt, eip = 0xc064d655, esp = 0xd763ace0, ebp = 0xd763ace0 --- > > This is almost certainly addressed by jhb's atpic patch. > > -Nate With a kernel built yesterday, they are working again. Awsome work guys. Go the Wallabies -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
EISA Adaptec 274X SCSI panic (ISRng related)
On Sat, 15 Nov 2003, Andy Farkas wrote: > My EISA AHA2740's don't work no more :( # grep ahc /var/run/dmesg.boot ahc0: at 0x2c00-0x2cff, irq 10 (level) ahc0: on eisa0 slot 2 ahc1: at 0x4c00-0x4cff, irq 11 (level) ahc1: on eisa0 slot 4 ahc2: port 0xf800-0xf8ff mem 0xf68fb000-0xf68fbfff irq 17 at device 11.0 on pci1 ahc2: Using left over BIOS settings ahc3: port 0xf400-0xf4ff mem 0xf68fa000-0xf68fafff irq 18 at device 12.0 on pci1 ahc3: Using left over BIOS settings The CD drive attached to ahc3 works ok. But ahc0 and ahc1 dont: # dd if=/dev/da0 of=/dev/null kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x8:0xc0649083 stack pointer = 0x10:0xd763ac5c frame pointer = 0x10:0xd763ac84 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 14 (idle: cpu0) kernel: type 12 trap, code=0 Stopped at intr_execute_handlers+0x23: lock addl %eax,0(%edx) db> tr intr_execute_handlers(c06d5084,d763ac9c,d763ace0,c065bbae,7) at intr_execute_handlers+0x23 atpic_handle_intr(7) at atpic_handle_intr+0x42 Xatpic_intr7() at Xatpic_intr7+0x1e --- interrupt, eip = 0xc064d655, esp = 0xd763ace0, ebp = 0xd763ace0 --- cpu_idle_default(d763ad0c,c04f523c,c06ea740,2,c068b1fa) at cpu_idle_default+0x5 cpu_idle(c06ea740,2,c068b1fa,53,14b) at cpu_idle+0x28 idle_proc(0,d763ad48,c068b09c,311,0) at idle_proc+0x3c fork_exit(c04f5200,0,d763ad48) at fork_exit+0xb4 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xd763ad7c, ebp = 0 --- db> Verbose dmesg at: http://www.speednet.com.au/~andyf/hummer/hummer-eisa-aha-crash -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5-CURRENT totally broken on AMD64 in 32-bit mode
On Mon, 17 Nov 2003, David O'Brien wrote: > The kernel changes of the past week has totally turned my AMD64 machine > that I use in 32-bit mode running FreeBSD/i386 (GENERIC): > > OK boot -v > cpuid = 0; apic id = 00 > instruction pointer = 0x0:0xa00 > stack pointer = 0x0:0xffe > frame pointer = 0x0:0x0 > code segment= base 0x0, limit 0x0, type 0x0 > = DPL 0 , pres 0, def32 0, gran 0 > processor eflags= interrupt enabled, vm86, IOPL = 0 > cuyrrent process= 0 () > kernel: type 30 trap, code=0 > Stopped at 0xa00: cli > db> tr > (null)(0,0,0,0,0) at 0xa00 The changes that break things were made more than a week ago. I sent this email last week: > Date: Sun, 9 Nov 2003 09:22:17 +1000 (EST) > From: Andy Farkas <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: kernel halts before booting > > My kernels now break into the debugger before booting! > > Boot sequence goes like this: > > ... > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [/boot/kernel/kernel]... > cpuid = 0; apic id = 00 > instruction pointer = 0x0:0xa00 > stack pointer = 0x0:0xffe > frame pointer = 0x0:0x0 > code segment= base 0x0, limit 0x0, type 0x0 > = DPL 0, pres 0, def32 0, gran 0 > processor eflags= interrupt enabled, vm86, IOPL = 0 > current process = 0 () > kernel: type 30 trap, code=0 > stopped at 0xa00: cli > db> My machine is a: > db> cont > Copyright (c) 1992-2003 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.1-CURRENT #0: Fri Nov 7 17:17:10 EST 2003 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TEAM2 > Preloaded elf kernel "/boot/kernel/kernel" at 0xc0751000. > MPTable: > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Pentium/P54C (132.00-MHz 586-class CPU) > Origin = "GenuineIntel" Id = 0x52c Stepping = 12 > Features=0x3bf > real memory = 134217728 (128 MB) > avail memory = 124928000 (119 MB) > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > Intel Pentium detected, installing workaround for F00F bug -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: checking stopevent 2!
Robert Watson wrote: > On Sat, 15 Nov 2003, Andy Farkas wrote: > > > These messages spew onto my console and into syslogd once every second: > > Heh. Sounds like your box is having a really bad day, we'll see if we > can't get it fixed up over the next couple of weeks as things settle out > :-). As you've probably noticed, this problem is pretty wide-spread. A fix better get in before 5.2-release please :) I've managed to stop the message flooding by not running ntpd. > IT would probably be useful if you could drop to DDB and generate a > trace for the event. Do you still want me to do this? I thought the messages themselves were supposed to useful: locked @ /hummer/src-current/src/sys/kern/kern_condvar.c:289 locked @ /hummer/src-current/src/sys/kern/kern_synch.c:293 locked @ /hummer/src-current/src/sys/kern/subr_trap.c:260 # ident /hummer/src-current/src/sys/kern/kern_condvar.c /hummer/src-current/src/sys/kern/kern_condvar.c: $FreeBSD: src/sys/kern/kern_condvar.c,v 1.44 2003/11/09 09:17:24 tanimura Exp $ # ident /hummer/src-current/src/sys/kern/kern_synch.c /hummer/src-current/src/sys/kern/kern_synch.c: $FreeBSD: src/sys/kern/kern_synch.c,v 1.237 2003/10/29 15:23:09 bde Exp $ # ident /hummer/src-current/src/sys/kern/subr_trap.c /hummer/src-current/src/sys/kern/subr_trap.c: $FreeBSD: src/sys/kern/subr_trap.c,v 1.261 2003/09/05 22:15:26 peter Exp $ -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dc still reporting collisions
Andy Farkas replies to himself: > The dc(4) driver currently has an almost 1:1 ratio of packets:collisions. > Your tx0 is quite low. Ack! I can't count. Or my numerical recognition system is failing NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll dc01500 00:00:e8:89:b9:6626463 026737 13253 225301 Ipkts + Opkts < collisions :( -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dc still reporting collisions
Jos Backus wrote: > Fwiw, I'm seeing the same with tx(4): Looks like a different problem. > lizzy:~% ifconfig tx0 > tx0: flags=8843 mtu 1500 > inet 10.0.0.2 netmask 0xff00 broadcast 10.0.0.255 > inet 10.0.0.10 netmask 0x broadcast 10.0.0.10 > ether 00:e0:29:09:e4:1a > media: Ethernet autoselect (10baseT/UTP) > status: active > lizzy:~% netstat -i > NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll > tx01500 00:e0:29:09:e4:1a 154423 1 118093 0 253 > tx01500 10/24 lizzy 159162 - 122841 - - > tx01500 10.0.0.10/32 lizzy-proxy 28 - 28 - - > lo0 16384 5347 0 5347 0 0 > lo0 16384 your-net localhost 442 - 442 - - > lizzy:~% The dc(4) driver currently has an almost 1:1 ratio of packets:collisions. Your tx0 is quite low. Seishi Hiragushi <[EMAIL PROTECTED]> reported this 1.5 months ago: Message-Id: <[EMAIL PROTECTED]> -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
dc still reporting collisions
The dc(4) driver is still reporting collisions on 100 Mbit full-duplex links: > grep dc0 /var/run/dmesg.boot dc0: port 0xd000-0xd0ff mem 0xfbfdf000-0xfbfdf0ff irq 10 at device 6.0 on pci0 dc0: Ethernet address: 00:00:e8:89:b9:66 miibus0: on dc0 > ifconfig -a dc0: flags=8843 mtu 1500 inet 172.22.2.12 netmask 0xfff0 broadcast 172.22.2.15 ether 00:00:e8:89:b9:66 media: Ethernet autoselect (100baseTX ) status: active > netstat -i NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll dc01500 00:00:e8:89:b9:6626463 026737 13253 225301 dc01500 172.22.2/28 team226044 -26636 - - lo0 16384 73 0 73 0 0 lo0 16384 your-net localhost 73 - 73 - - -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
console freezes
When messages are sent to console rapidly, console becomes unavailable :( My previous email complains of messages being spewed to the console. These messages stop after a few minutes and the console is dead. On another box of mine, same thing happens. Different messages get spewed to console and it locks up (I am preparing another email about it, messages are ATA related) -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
EISA AHA panic (ISRng related)
My EISA AHA2740's don't work no more :( If I 'dd if=/dev/da0 of=/dev/null' with -CURRENT cvsup'd a few hours ago, I get this panic: ... kernel: type 12 trap, code=0 Stopped at intr_execute_handlers+0x23: lock addl%eax,0(%edx) db> where intr_execute_handlers(c06d3d04,d763ac9c,d763ace0,c065aafe,7) at intr_execute_handlers+0x23 atpic_handle_intr(7) at apic_handle_intr+0x42 Xatpic_intr7() at Xatpic_intr7+0x1e ... Verbose dmesg's at: http://www.speednet.com.au/~andyf/hummer/hummer-dmesg.boot-current http://www.speednet.com.au/~andyf/hummer/hummer-dmesg.boot-release -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
checking stopevent 2!
Help! These messages spew onto my console and into syslogd once every second: ... Nov 15 16:05:44 hummer kernel: checking stopevent 2 with the following non-sleepable locks held: Nov 15 16:05:44 hummer kernel: exclusive sleep mutex sigacts r = 0 (0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/kern_condvar.c:289 Nov 15 16:05:44 hummer kernel: checking stopevent 2 with the following non-sleepable locks held: Nov 15 16:05:44 hummer kernel: exclusive sleep mutex sigacts r = 0 (0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/subr_trap.c:260 Nov 15 16:05:44 hummer kernel: checking stopevent 2 with the following non-sleepable locks held: Nov 15 16:05:45 hummer kernel: exclusive sleep mutex sigacts r = 0 (0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/subr_trap.c:260 Nov 15 16:05:45 hummer kernel: checking stopevent 2 with the following non-sleepable locks held: Nov 15 16:05:45 hummer kernel: exclusive sleep mutex sigacts r = 0 (0xc4663aa8) locked @ /hummer/src-current/src/sys/kern/kern_synch.c:293 Nov 15 16:05:45 hummer kernel: checking stopevent 2 with the following non-sleepable locks held: Nov 15 16:05:45 hummer kernel: exclusive sleep mutex sigacts r = 0 (0xc4663aa8) locked @ /hummer/src-current/src/sys/kern/subr_trap.c:260 Nov 15 16:05:45 hummer kernel: checking stopevent 2 with the following non-sleepable locks held: Nov 15 16:05:45 hummer kernel: exclusive sleep mutex sigacts r = 0 (0xc4663aa8) locked @ /hummer/src-current/src/sys/kern/subr_trap.c:260 Nov 15 16:05:45 hummer kernel: checking stopevent 2 with the following non-sleepable locks held: Nov 15 16:05:45 hummer kernel: exclusive sleep mutex sigacts r = 0 (0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/kern_condvar.c:289 Nov 15 16:05:45 hummer kernel: checking stopevent 2 with the following non-sleepable locks held: Nov 15 16:05:46 hummer kernel: exclusive sleep mutex sigacts r = 0 (0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/subr_trap.c:260 Nov 15 16:05:46 hummer kernel: checking stopevent 2 with the following non-sleepable locks held: Nov 15 16:05:46 hummer kernel: exclusive sleep mutex sigacts r = 0 (0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/kern_condvar.c:289 Nov 15 16:05:46 hummer kernel: checking stopevent 2 with the following non-sleepable locks held: Nov 15 16:05:46 hummer kernel: exclusive sleep mutex sigacts r = 0 (0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/subr_trap.c:260 Nov 15 16:05:46 hummer kernel: checking stopevent 2 with the following non-sleepable locks held: Nov 15 16:05:46 hummer kernel: exclusive sleep mutex sigacts r = 0 (0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/subr_trap.c:260 ... This is latest -current (cvsup'd a few hours ago) -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ATAng 'mode PIO4' to 'mode ???' regression
-current (cvsup'd about 3 hours ago) doesn't like my ATA disk anymore :( 5.1-RELEASE says (during 'boot -v'): ata0: pre reset mask=03 ostat0=50 ostat2=00 ata0-master: ATAPI 00 00 ata0-slave: ATAPI 00 00 ata0: after reset mask=03 stat0=50 stat1=00 ata0-master: ATA 01 a5 ata0: devices=01 ata0 at port 0x3f6,0x1f0-0x1f7 irq 14 on isa0 ata1 at port 0x376,0x170-0x177 irq 15 on isa0 ad0: ATA-0 disk at ata0-master ad0: 1222MB (2503872 sectors), 2484 C, 16 H, 63 S, 512 B ad0: 1 secs/int, 1 depth queue, PIO4 ad0: piomode=12 dmamode=34 udmamode=-1 cblid=0 But -CURRENT says (during 'boot -v'): ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata0-slave: stat=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 mask=03 stat0=50 stat1=00 devices=0x1 ata0 at port 0x3f6,0x1f0-0x1f7 irq 14 on isa0 ata0: [MPSAFE] ata1 at port 0x376,0x170-0x177 irq 15 on isa0 ata1: [MPSAFE] ad0: ATA-0 disk at ata0-master ad0: 1222MB (2503872 sectors), 2484 C, 16 H, 63 S, 512 B ad0: 1 secs/int, 1 depth queue, ??? Notice the "???" ? Verbose dmesg's at: http://www.speednet.com.au/~andyf/hummer/hummer-dmesg.boot-current http://www.speednet.com.au/~andyf/hummer/hummer-dmesg.boot-release -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: signal 12's everywhere on Current with update this morning.
Richard Coleman wrote: > 1. make buildworld > 2. make buildkernel KERNCONF=NAME_OF_KERNEL_FILE > 3. make installkernel KERNCONF=NAME_OF_KERNEL_FILE > 4. shutdown -r now > 5. boot into single user mode > 6. fsck -p > 7. mount -u / > 8. mount -a -t ufs > 9. swapon -a 9.5 adjkerntz -i > 10. make installworld > 11. mergemaster > 12. reboot ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: making a release
Scott Long wrote: > I use the following all of the time: > > cd /usr/src/release ; make release BUILDNAME=5.1-CURRENT > CHROOTDIR=/usr/release CVSROOT=/usr/ncvs Quick question: is it ok to do make -j release ? -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
kernel halts before booting
My kernels now break into the debugger before booting! Boot sequence goes like this: ... Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... cpuid = 0; apic id = 00 instruction pointer = 0x0:0xa00 stack pointer = 0x0:0xffe frame pointer = 0x0:0x0 code segment= base 0x0, limit 0x0, type 0x0 = DPL 0, pres 0, def32 0, gran 0 processor eflags= interrupt enabled, vm86, IOPL = 0 current process = 0 () kernel: type 30 trap, code=0 stopped at 0xa00: cli db> cont Copyright (c) 1992-2003 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.1-CURRENT #0: Fri Nov 7 17:17:10 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TEAM2 Preloaded elf kernel "/boot/kernel/kernel" at 0xc0751000. MPTable: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium/P54C (132.00-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x3bf real memory = 134217728 (128 MB) avail memory = 124928000 (119 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 Intel Pentium detected, installing workaround for F00F bug ioapic0: Assuming intbase of 0 ioapic0 irqs 0-15 on motherboard ACPI-0159: *** Error: AcpiLoadTables: Could not get RSDP, AE_NO_ACPI_TABLES ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_NO_ACPI_TABLES ACPI: table load failed: AE_NO_ACPI_TABLES npx0: [FAST] ... Also happens with GENERIC. -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problems with sysinstall
Sergey Matveychuk wrote: > Richard Nyberg wrote: > >Doug White wrote: > > > yes, this is a change to -current. It is for your own safety. > > > > I think this change in current is for the worse. I don't see why > > I can't manage slices and partitions from my regular OS, but have > > to boot up a CD to do the job. It's not even safer; I am perfectly > > capable of destroying my disk layout from the CD too. > > Agree. Why I can't change active slice? Or add a partition? Or repair my > master boot record? > It's absolutely safe. Its a major PITA and POLA violation IMHO. The super-user should be able to foot-shoot whatever she wants to. For example, you setup a production box with a 60 gig disk. You allocate 40 gig initially, leaving 20 gig as "reserve". Time passes. You now need that extra 20 gig but can not down the server. You are stuffed. -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
scheduling
Not to flog a dead horse, but scheduling seems to be very broken this month. I am subjectively watching my smp box do a: 'cd /usr/ports/www/apache2 ; make all' in one window, and 'cd cd /usr/ports/databases/mysql40-server/ ; make all' in another window, and most disturbingly a 'top -S' in a 3rd window reporting 42.63% idle on cpu0, 39.50% idle on cpu1. It just doesn't seem right to me. -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Syncer "giving up" on buffers
Jeff Roberson wrote: > I don't know of any general syncer issues outside of this. Boot single user, run fsck, then halt. -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: current: network collition increase
Seishi Hiragushi wrote: > I noticed that network collition increase, in log of 7/26. > Such still a state continues. > What became like this owing to? > > 5.1-CURRENT-20030720 (daily run 7/26): > Network interface status: > NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll > dc01500 00:90:cc:a2:59:56 38342027 441061 0 260568 > dc01500 192.168.200 * 374698 - 431325 - - > dc11500 00:c0:ca:10:91:89 190866 0 136617 4124 70128 ... > dc0: flags=8843 mtu 1500 > inet 192.168.200.1 netmask 0xff00 broadcast 192.168.200.255 > inet6 fe80::2c0:caff:fe10:918c%dc0 prefixlen 64 scopeid 0x1 > ether 00:c0:ca:10:91:8c > media: Ethernet autoselect (100baseTX ) > status: active I am seeing the same thing: team2# netstat -inr NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll dc01500 00:00:e8:89:b9:66 1205836 0 899804 171173 2909941 dc01500 172.22.2/28 172.22.2.121205560 - 899768 - - lo0 16384 52 0 52 0 0 lo0 16384 127 127.0.0.1 52 - 52 - - team2# team2# ifconfig dc0 dc0: flags=8843 mtu 1500 inet 172.22.2.12 netmask 0xfff0 broadcast 172.22.2.15 ether 00:00:e8:89:b9:66 media: Ethernet autoselect (100baseTX ) status: active Collisions shouldn't happen on a full-duplex link? -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Syncer failure after fsck on all partitions
Kevin Oberman wrote: > Finally I do a reboot. No partition has ever been mounted except root > which is read-only. Syncer reports 1 or more buffers remain and > reports this until it gives up. On Tue, 29 Jul 2003 08:13:27 +1000 (EST) Andy Farkas <[EMAIL PROTECTED]> wrote: > Subject: buffers remaining... > > If you boot into single user mode (boot -s), do an fsck (a full fsck, no > options), then halt(8), you will get: > > syncing disks, buffers remaining... 1 1 1 1 1 1 1 1 1 1 > giving up on 1 buffers Nobody responded. It must not matter. -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: current: network collition increase
On Tue, 2 Sep 2003, Seishi Hiragushi wrote: > 5.1-CURRENT-20030720 (daily run 7/26): > Network interface status: > NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll > dc01500 00:90:cc:a2:59:56 38342027 441061 0 260568 ^ Above is a different nic than below: > dc0: port 0xa000-0xa07f mem 0xe580-0xe580007f irq 4 > at device 10.0 on pci0 > dc0: Ethernet address: 00:c0:ca:10:91:8c ^ -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: smp in 5.1
On Mon, 11 Aug 2003, Eriq Lamar wrote: > Is there any advantage in 5.1 over 4.8 for two amd mp's. and if so could > someone tell what they are. I am interested in building dual system using > mp's but not sure which version would be better. Scheduling in 5.1 is broken (sched_ule doesn't even work*). Stick with 4.8. * for me, sched_ule completely locks up my box, no ping, no keybd. Exact same kernel with sched_4bsd works fine. -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: INET6 in world
On Sun, 3 Aug 2003, Bernd Walter wrote: > On Sun, Aug 03, 2003 at 04:07:15PM +0200, Jens Rehsack wrote: > > Hi David, > > > > I've seen that several world daemons (rpcbind, telnetd, ...) are > > build with INET6. > > In real life, I do not know anyone who owns some IPv6 addresses > > but many guys who disabled INET6 on their machines in kernel. ... > No daemon explicitly binds to an inet6 socket unless configured > to do so. During bootup, I see this too: Jul 13 18:09:42 hummer kernel: Starting rpcbind. Jul 13 18:09:42 hummer kernel: Jul 13 18:09:42 hummer rpcbind: cannot create socket for udp6 Jul 13 18:09:42 hummer kernel: Jul 13 18:09:42 hummer rpcbind: cannot create socket for tcp6 -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
buffers remaining...
If you boot into single user mode (boot -s), do an fsck (a full fsck, no options), then halt(8), you will get: syncing disks, buffers remaining... 1 1 1 1 1 1 1 1 1 1 giving up on 1 buffers every time. Only happens with clean disks. 100% reproducable. I have UFS1 partitions. Been happening for quite a while (since 5.0) -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SMP and setrunnable()- scheduler 4bsd
> Mr Wolf, Heh, you noticed :) > > Currently (cpu_idle_hlt=1) the load is fluctuating between 2.20 and 3.60 > > every few minutes! (xload looks like a graph of a sinewave) > > > > If I set cpu_idle_hlt back to 0 the load goes back to a steady 3.80 where > > it should be. > > define "should". When all 3 seti's get their "normal" 95% cpu time: 32531 setiathome 139 15 16536K 15520K *Giant 1 60.9H 95.85% 95.85% setiathome 32533 setiathome 139 15 16856K 16032K CPU3 3 61.0H 95.65% 95.65% setiathome 32532 setiathome 139 15 15524K 14912K CPU2 2 60.8H 95.51% 95.51% setiathome 54738 andyf 1320 3084K 2140K *Giant 0 64:54 83.84% 83.84% ssh 12 root -160 0K12K RUN2 133.4H 3.81% 3.81% idle: cpu2 13 root -160 0K12K RUN1 131.7H 3.47% 3.47% idle: cpu1 14 root -160 0K12K CPU0 0 130.8H 3.37% 3.37% idle: cpu0 11 root -160 0K12K RUN3 135.2H 2.88% 2.88% idle: cpu3 As opposed to "abnormal" when cpu_idle_hlt=1: 32533 setiathome 139 15 15828K 15000K CPU1 2 61.0H 89.40% 89.40% setiathome 32532 setiathome 139 15 16552K 15660K *Giant 2 60.8H 88.18% 88.18% setiathome 54738 andyf 1300 3084K 2140K select 2 68:54 75.78% 75.78% ssh 13 root -160 0K12K RUN1 131.7H 29.05% 29.05% idle: cpu1 12 root -160 0K12K CPU2 2 133.4H 28.08% 28.08% idle: cpu2 11 root -160 0K12K CPU3 3 135.2H 27.83% 27.83% idle: cpu3 14 root -160 0K12K RUN0 130.8H 26.37% 26.37% idle: cpu0 32531 setiathome 131 15 15640K 14976K *Giant 2 61.0H 20.51% 20.51% setiathome -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SMP and setrunnable()- scheduler 4bsd
On Wed, 9 Jul 2003, Terry Lambert wrote: > Andy Farkas wrote: > > On Tue, 8 Jul 2003, Julian Elischer wrote: > > > It looks tp me that if we make a thread runnable > > > and there is a processor in the idle loop, the idle processor should be > > > kicked in some way to make it go get the newly runnable thread. > > > > Is this what's happenning to me an my setiathomes? > > The command: > > sysctl machdep.cpu_idle_hlt > > will tell you. If it says 1, then it may be the problem. If it > says 0, then it's not the problem. You can explicitly set it to > zero to disable halting in the idle loop. If you do this, your > machine is likely to run ~20% hotter (depending on the CPU type), > since HLT'ing an idle CPU tends to cool it off. > > If this fixes your problem, then it's likely that what's happening > is that one or more of your CPU's are being idled until the clock > or some other interrupt fires, at which point in time your setiathome > processes are probably not the highest priority, as other things with > higher priority have gotten in the run queue ahead of them. > > If this is the case, then Julian's suggested fix of an IPI to one or > more idle CPU's when a process becomes ready-to-run will most likely > be necessary to avoid this situation. Well, looks like machdep.cpu_idle_hlt affects the 4bsd scheduler. Julian, have your patches at http://www.freebsd.org/~julian/it.diff been incorporated yet? SHould I try them? hummer# sysctl -a | grep kern.ver kern.version: FreeBSD 5.1-RELEASE #0: Thu Jun 26 01:57:42 EST 2003 hummer# sysctl -a | grep cpu kern.threads.virtual_cpu: 4 kern.ccpu: 1948 <--- whats this? kern.smp.cpus: 4 hw.ncpu: 4 machdep.cpu_idle_hlt: 0 machdep.hlt_cpus: 0 hummer# hummer# vmstat -c 12 -w 10 procs memory pagedisks faults cpu r b w avmfre flt re pi po fr sr ad0 am0 in sy cs us sy id 1 1 3 124804 20792 99 0 0 0 131 20 0 0 3620 544 33 3 64 2 1 2 125240 32460 197 0 0 0 358 258 0 1 3650 2161 67 26 7 2 1 2 124728 32204 214 0 0 0 249 0 0 1 3820 1280 72 23 5 1 1 3 124112 29652 257 0 0 0 247 0 3 1 4140 1571 70 25 5 3 1 1 124624 26020 236 0 0 0 297 0 0 1 3730 1367 70 24 7 2 1 2 124792 25464 222 0 0 0 266 0 2 1 4080 1308 72 24 4 3 1 1 123764 25172 203 0 0 0 227 0 0 1 3800 1053 72 23 5 3 1 2 124164 22004 229 0 0 0 264 0 0 1 3710 1164 72 25 3 3 1 2 124796 20232 208 0 0 0 262 0 1 1 3830 1269 72 23 5 3 1 1 123768 20448 225 0 0 0 252 0 0 1 3740 1306 72 25 3 3 1 0 122736 33736 214 0 0 0 458 194 0 1 3630 1341 72 24 4 3 1 1 123380 32008 236 0 0 0 222 0 2 1 4050 1430 72 25 4 hummer# hummer# sysctl machdep.cpu_idle_hlt=1 machdep.cpu_idle_hlt: 0 -> 1 hummer# vmstat -c 12 -w 10 procs memory pagedisks faults cpu r b w avmfre flt re pi po fr sr ad0 am0 in sy cs us sy id 2 1 1 124760 20848 99 0 0 0 131 20 0 0 3620 544 33 3 64 1 1 3 123948 20844 157 0 0 0 191 0 0 1 3850 1142 51 21 28 2 1 2 124408 20472 134 0 0 0 176 0 0 1 3720 1118 48 22 30 2 1 1 124992 18800 179 0 0 0 181 0 1 2 3940 1147 49 20 31 2 2 3 123792 31228 162 0 0 0 367 196 0 1 3780 48 21 30 1 1 4 124348 30048 175 0 0 0 169 0 0 1 3680 1084 51 22 27 2 0 4 18 29140 142 0 0 0 193 0 1 2 3990 1056 53 21 26 2 1 2 124688 25324 176 0 0 0 135 0 0 1 3700 1138 47 21 31 2 1 1 122632 26572 136 0 0 0 209 0 0 1 3740 1110 50 21 30 2 1 2 122288 26036 162 0 0 0 193 0 1 2 3840 1152 49 22 29 2 1 2 122288 25204 136 0 0 0 157 0 0 1 3690 1101 50 21 29 2 1 2 122700 23720 172 0 0 0 183 0 0 1 3760 1123 48 21 31 Currently (cpu_idle_hlt=1) the load is fluctuating between 2.20 and 3.60 every few minutes! (xload looks like a graph of a sinewave) If I set cpu_idle_hlt back to 0 the load goes back to a steady 3.80 where it should be. -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SMP and setrunnable()- scheduler 4bsd
On Tue, 8 Jul 2003, Julian Elischer wrote: > It looks tp me that if we make a thread runnable > and there is a processor in the idle loop, the idle processor should be > kicked in some way to make it go get the newly runnable thread. Is this what's happenning to me an my setiathomes? -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: whats going on with the scheduler?
On Tue, 8 Jul 2003, Doug White wrote: > On Tue, 8 Jul 2003, Andy Farkas wrote: > > > Any other ideas? Why would 3 (niced) cpu intensive processes suddenly get > > reduced cpu time (on a 4 cpu system) when a 4th non-resource intensive > > process gets started? > > Hm.. guess its time to explain how nice works again. > > Nice is a relative value. If you have 2 processes in a system, one with a > lower nice value (== higher "priority") than the other, the lower-niced > process will be scheduled in deference to the higher-niced process. The > scheduler attempts to ensure that niced processes are not starved. (In > practice, nice level 20 gets some special treatment.) That doesn't explain why the idle time goes up, in my case. If you have 4 processors in a box and start 3 cpu-intensive jobs, the system load will be 3.00 and idle time will be 25%. If you start another semi cpu-intensive process, one would expect the load to increase and the idle time to come down, regardless if the other 3 procs are niced or not. ps. setiathome procs run at idle level 15. -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: whats going on with the scheduler?
On Tue, 8 Jul 2003, Terry Lambert wrote: > Dan Nelson wrote: > > In the last episode (Jul 08), Andy Farkas said: > > > If setiathome is making lots of syscalls, then running the 3 instanses > > > should already show a problem, no? > > > > Not if it's ssh that's holding Giant for longer than it should. The > > setiathome processes may be calling some really fast syscall 500 times > > a second which doesn't cause a problem until ssh comes along and calls > > some other syscall that takes .1 ms to return but also locks Giant long > > enough to cause the other processes to all back up behind it. > > Specifically, if it's sleeping with Giant held because the > Send-Q is full (use netstat to check) it could block things > for a long time, waiting for the queue to drain. scp was retrieving a file, not sending, and it was bandwidth limited. Any other ideas? Why would 3 (niced) cpu intensive processes suddenly get reduced cpu time (on a 4 cpu system) when a 4th non-resource intensive process gets started? Also, from something that BDE said once, this command will produce unexpected results when run for more than a few hours: for i in `jot -n -s ' ' 20 0 19 1` do nice -$i sh -c "while :; do echo -n;done" & done -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: whats going on with the scheduler?
On Tue, 8 Jul 2003, Terry Lambert wrote: > It's not clear what your link speed is, but it's possible that > what's happening is that the setiathome processes are stalling > waiting for work units because you are using up your available > network bandwidth. setiathome is a cpu intensive process. It touches the network maybe once in a 24 hour period when it downloads a ~400k work unit which takes less than 10 seconds over my 512k/128k dsl link and then proceeds to number crunch. Stalling on work units is not whats happening. > If this is what's ahppening, you might want to try bandwidth > limiting the scp and/or running with Alt-Q and/or begging Julian I *did* limit scp: > scp -c blowfish -p -l 100 remote.host:filename . -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: whats going on with the scheduler?
On Mon, 7 Jul 2003, Dan Nelson wrote: > Not if it's ssh that's holding Giant for longer than it should. The > setiathome processes may be calling some really fast syscall 500 times > a second which doesn't cause a problem until ssh comes along and calls > some other syscall that takes .1 ms to return but also locks Giant long > enough to cause the other processes to all back up behind it. setiathome seems to only make syscalls once every few seconds: 50.625740361 open("outfile.sah",0x0,0666)= 5 (0x5) 50.632149151 fstat(5,0xbfbff7bc) = 0 (0x0) 50.638742382 fstat(5,0xbfbff874) = 0 (0x0) 50.646472300 lseek(5,0x0,1) = 0 (0x0) 50.654260852 lseek(5,0x0,0) = 0 (0x0) 50.660798154 read(0x5,0xe65000,0x4000) = 3756 (0xeac) 50.667928862 close(5)= 0 (0x0) 50.674330474 getrusage(0x0,0xbfbff994) = 0 (0x0) 50.685590259 open("outfile.sah",0x0,0666)= 5 (0x5) 50.694391188 fstat(5,0xbfbff7ac) = 0 (0x0) 50.703441591 fstat(5,0xbfbff864) = 0 (0x0) 50.711881896 lseek(5,0x0,1) = 0 (0x0) 50.719670900 lseek(5,0x0,0) = 0 (0x0) 50.725983906 read(0x5,0xd64000,0x4000) = 3756 (0xeac) 50.732710339 close(5)= 0 (0x0) 54.227980065 open("outfile.sah",0x0,0666)= 5 (0x5) 54.234289708 fstat(5,0xbfbff7bc) = 0 (0x0) 54.241518075 fstat(5,0xbfbff874) = 0 (0x0) 54.249555307 lseek(5,0x0,1) = 0 (0x0) 54.257416703 lseek(5,0x0,0) = 0 (0x0) 54.263766467 read(0x5,0xe65000,0x4000) = 3756 (0xeac) 54.270554826 close(5)= 0 (0x0) 54.276730780 getrusage(0x0,0xbfbff994) = 0 (0x0) 54.286228233 open("outfile.sah",0x0,0666)= 5 (0x5) 54.292575368 fstat(5,0xbfbff7ac) = 0 (0x0) 54.299568244 fstat(5,0xbfbff864) = 0 (0x0) 54.313140514 lseek(5,0x0,1) = 0 (0x0) 54.320997075 lseek(5,0x0,0) = 0 (0x0) 54.327394776 read(0x5,0xd64000,0x4000) = 3756 (0xeac) 54.334797742 close(5)= 0 (0x0) 57.830104692 open("outfile.sah",0x0,0666)= 5 (0x5) 57.836412958 fstat(5,0xbfbff7bc) = 0 (0x0) 57.842768341 fstat(5,0xbfbff874) = 0 (0x0) 57.850834611 lseek(5,0x0,1) = 0 (0x0) 57.862301512 lseek(5,0x0,0) = 0 (0x0) 57.868723869 read(0x5,0xe65000,0x4000) = 3756 (0xeac) 57.875396846 close(5)= 0 (0x0) 57.881638118 getrusage(0x0,0xbfbff994) = 0 (0x0) 57.890991955 open("outfile.sah",0x0,0666)= 5 (0x5) 57.897344227 fstat(5,0xbfbff7ac) = 0 (0x0) 57.903621248 fstat(5,0xbfbff864) = 0 (0x0) 57.913178984 lseek(5,0x0,1) = 0 (0x0) 57.922614702 lseek(5,0x0,0) = 0 (0x0) 57.931253628 read(0x5,0xd64000,0x4000) = 3756 (0xeac) 57.938755028 close(5)= 0 (0x0) -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: whats going on with the scheduler?
On Mon, 7 Jul 2003, Dan Nelson wrote: > > I bet those *Giants have something to do with it... > > Most likely. That means they're waiting for some other process to > release the big Giant kernel lock. Paste in top's header so we can see > how many processes are locked, and what the system cpu percentage is. This is what top looks like (up to the 1st 0.00% process) when sitting idle* with 3 setiathomes: last pid: 50290; load averages: 3.02, 3.07, 3.06 up 8+23:24:11 14:00:47 97 processes: 9 running, 71 sleeping, 4 zombie, 12 waiting, 1 lock CPU states: 4.0% user, 72.0% nice, 4.6% system, 0.7% interrupt, 18.8% idle Mem: 142M Active, 220M Inact, 116M Wired, 19M Cache, 61M Buf, 1916K Free Swap: 64M Total, 128K Used, 64M Free PID USERNAME PRI NICE SIZERES STATE C TIME WCPUCPU COMMAND 42946 setiathome 139 15 16552K 15984K RUN0 43.8H 98.00% 98.00% setiathome 42945 setiathome 139 15 16944K 15732K CPU1 1 43.0H 97.56% 97.56% setiathome 42947 setiathome 139 15 15524K 14956K CPU0 2 42.9H 94.14% 94.14% setiathome 14 root -160 0K12K RUN0 144.7H 21.97% 21.97% idle: cpu0 12 root -160 0K12K RUN2 153.5H 19.87% 19.87% idle: cpu2 11 root -160 0K12K RUN3 153.6H 18.60% 18.60% idle: cpu3 13 root -160 0K12K RUN1 150.2H 17.29% 17.29% idle: cpu1 50090 root 1110 11884K 11084K CPU3 3 4:22 11.57% 11.57% cdparanoia 12571 andyf 1000 20488K 19308K select 1 509:56 4.00% 4.00% XFree86 17629 andyf 970 2676K 1624K select 3 244:57 1.03% 1.03% xdaliclock 16 root -48 -167 0K12K *Giant 1 122:57 0.39% 0.39% swi7: tty:sio clock 38 root200 0K12K syncer 0 101:47 0.00% 0.00% syncer *I'm running an X desktop and right now I'm ripping a cd but as you can see its not doing much else.. Note how the seti procs are getting 94-98% cpu time. When I do my scp thing, top looks like this: last pid: 50322; load averages: 1.99, 2.82, 2.98 up 8+23:39:09 14:15:45 98 processes: 8 running, 71 sleeping, 4 zombie, 12 waiting, 3 lock CPU states: 1.7% user, 33.7% nice, 20.1% system, 0.6% interrupt, 43.9% idle Mem: 135M Active, 224M Inact, 120M Wired, 19M Cache, 61M Buf, 1424K Free Swap: 64M Total, 128K Used, 64M Free PID USERNAME PRI NICE SIZERES STATE C TIME WCPUCPU COMMAND 42946 setiathome 139 15 16552K 15984K CPU3 2 44.0H 68.41% 68.41% setiathome 50296 andyf 1250 3084K 2176K RUN2 7:55 64.21% 64.21% ssh 12 root -160 0K12K CPU2 2 153.6H 48.78% 48.78% idle: cpu2 11 root -160 0K12K CPU3 3 153.6H 48.63% 48.63% idle: cpu3 13 root -160 0K12K RUN1 150.2H 48.44% 48.44% idle: cpu1 14 root -160 0K12K RUN0 144.8H 45.31% 45.31% idle: cpu0 42947 setiathome 130 15 15524K 14956K RUN2 43.1H 28.56% 28.56% setiathome 42945 setiathome 125 15 15916K 14700K RUN0 43.2H 25.05% 25.05% setiathome 50090 root-80 5636K 4832K cbwait 3 5:21 2.69% 2.69% cdparanoia 12571 andyf 970 20488K 19308K select 1 510:43 2.39% 2.39% XFree86 16 root -48 -167 0K12K *Giant 0 123:11 0.98% 0.98% swi7: tty:sio clock 17629 andyf 970 2676K 1624K *Giant 0 245:18 0.93% 0.93% xdaliclock 38 root200 0K12K syncer 1 101:54 0.20% 0.20% syncer 50295 andyf80 2528K 1256K nanslp 0 0:03 0.05% 0.05% scp 28905 root 80 0K12K nfsidl 0 93:02 0.00% 0.00% nfsiod 0 Notice how 'nice' has gone to 33.7% and 'idle' to 43.9%, and the seti procs have dropped well below 94%. > A truss of one of the seti processes may be useful too. setiathome > really shouldn't be doing many syscalls at all. If setiathome is making lots of syscalls, then running the 3 instanses should already show a problem, no? -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: whats going on with the scheduler?
On 7 Jul 2003, Lanny Baron wrote: > A load of 3 is pretty high. I think you have more going on. Not for my box. Its only running at 75% cpu power. Its got four processors, so a load of 4 is when its running flat out. And I also said that the box is idle other than the 3 setiathomes. What I'm trying to find out is why at load 3 when adding another semi-cpu intensive process, the load starts fluctuating between 2 and 3, when it should go to a steady 3.4 or something. So the load actually goes down when I run another process! -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
whats going on with the scheduler?
FreeBSD 5.1-RELEASE with SCHED_4BSD on a quad ppro 200 (dell 6100/200). Last night I started 3 setiathome's then went to bed. The system was otherwise idle and had a load of 3.00, 3.00, 3.00. This morning, I wanted to copy a (large) file from a remote server, so I did a: scp -c blowfish -p -l 100 remote.host:filename . which is running in another window (and will run for 3 more hours). And now, on my otherwise idle system, the load is varying from less than 2.00 (!) to just over 3.00, with an average average of about 2.50. Here is some output from top: PID USERNAME PRI NICE SIZERES STATE C TIME WCPUCPU COMMAND 42946 setiathome 139 15 15524K 14952K *Giant 0 39.9H 89.26% 89.26% setiathome 49332 andyf 1300 3084K 2176K *Giant 2 81:49 67.68% 67.68% ssh 12 root -160 0K12K CPU2 2 152.1H 49.12% 49.12% idle: cpu2 13 root -160 0K12K CPU1 1 148.7H 44.58% 44.58% idle: cpu1 11 root -160 0K12K RUN3 152.1H 44.14% 44.14% idle: cpu3 14 root -160 0K12K CPU0 0 143.3H 41.65% 41.65% idle: cpu0 42945 setiathome 129 15 15916K 14700K *Giant 2 39.0H 25.20% 25.20% setiathome 42947 setiathome 129 15 15524K 14956K *Giant 1 40.3H 22.61% 22.61% setiathome So, can someone explain why the seti procs are not getting 100% cpu like they were before the scp(ssh) started and why there is so much idle time? I bet those *Giants have something to do with it... -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
smp idle pigs
With recent -current, in the :pigs page of systat(1) I've noticed that idle time gets displayed on NCPU+1 lines: NCPU=2: /0 /10 /20 /30 /40 /50 /60 /70 /80 /90 /100 root idle: cpu0 root idle: cpu1 NCPU=4: /0 /10 /20 /30 /40 /50 /60 /70 /80 /90 /100 XX root idle: cpu3 XX root idle: cpu2 XX root idle: cpu0 XX root idle: cpu1 XX No biggy, but maybe someone can have a look at it... -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Volunteer with genuine i386 cpu & lots of time wanted.
On Wed, 26 Feb 2003, Poul-Henning Kamp wrote: > Is there anybody out there who can try to run a straight -current > on a _real_ i386 class CPU ? > > Ie, not a i486, not a Cyrix, not an AMD but a genuine Intel i386DX > (SX would be but too suicidal to be informative). Well, finally got a kernel to boot on a 16MHz 386SX (suicidal is an understatement!) - will this do? (Actually, the box is a AST Bravo/286 with the 80286 CPU replaced with a 386SX upgrade. The company I used to work for made various CPU upgrade products for 286's and 386's in the early 90's, especially for IBM PS/2's) Had to patch the npx_attach() function in src/sys/i386/isa/npx.c to get it to work though. It seems revision 1.131 broke FPU-less CPU support: (bad bde, no cookie) > diff -u npx.c-orig npx.c --- npx.c-orig Wed Mar 5 11:42:49 2003 +++ npx.c Wed Mar 5 11:43:27 2003 @@ -495,7 +495,7 @@ } npxinit(__INITIAL_NPXCW__); - if (npx_cleanstate_ready == 0) { + if (npx_cleanstate_ready == 0 && npx_exists) { s = intr_disable(); stop_emulating(); fpusave(&npx_cleanstate); I'll try and get some data for your clock/time tracking requests in a few days. I assume you want wall-clock tracking info for both with and without ntpd running? > I am also not interested in people running heavily modified source > trees, it is -current I am interested in. (It's OK to fiddle the > kernel config and hints of course.) > > If somebody has the time and inclination, I have a number of questions > I would like answers to: > > 1. Does -current even boot on that vintage of hardware any more ? > > 2. Does it survive a kernel (GENERIC) build ? > 2a. Does the clock track wall-clock time correctly while doing so ? > > 3. Does it survive a buildworld ? > 3a. Does the clock track wall-clock time correctly while doing so ? > > 4. Can ntpd run against some random (but decent) NTP server steer > the clock ? > 1) If the machine is idle > 2) During buildworld. > Please notice if > a) ntpd resorts to clock steps > b) ntpd exits > c) ntpd core dumps > > Thanks in advance! > -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Volunteer with genuine i386 cpu & lots of time wanted.
On Thu, 27 Feb 2003 [EMAIL PROTECTED] wrote: > You need to compile a kernel with this > "cpu I386_CPU" > in your config file. > Seems you can't build a "cpu I386_CPU" only kernel! ie: # grep CPU GENERIC cpu I386_CPU #cpuI486_CPU #cpuI586_CPU #cpuI686_CPU # make buildkernel KERNCONF=GENERIC ... cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/dev -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter -D_KERNEL -include opt_global.h -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /usr/src/sys/i386/i386/identcpu.c cc1: warnings being treated as errors /usr/src/sys/i386/i386/identcpu.c: In function `printcpuinfo': /usr/src/sys/i386/i386/identcpu.c:145: warning: unused variable `brand' machine/specialreg.h: At top level: /usr/src/sys/i386/i386/identcpu.c:99: warning: `cpu_brand' defined but not used /usr/src/sys/i386/i386/identcpu.c:103: warning: `cpu_brandtable' defined but not used *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 :( -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
LOR when halt(8)ing
I get this everytime I halt(8) my box: # sync # sync # sync # halt boot() called on cpu#0 Waiting (max 60 seconds) for system process `vnlru' to stop...stopped Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped Waiting (max 60 seconds) for system process `syncer' to stop...stopped syncing disks, buffers remaining... 7 7 done lock order reversal 1st 0xc1920234 process lock (process lock) @ /usr/src/sys/kern/vfs_mount.c:1144 2nd 0xc244e634 filedesc structure (filedesc structure) @ /usr/src/sys/kern/vfs_mount.c:1151 Uptime: 12h28m0s The operating system has halted. Please press any key to reboot. -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
couple trivial todo's
- In src/share/examples/etc/make.conf NO_BIND=true should be moved up - the man page for splash(4) is missing descriptions for apm_saver.ko, dragon_saver.ko and fire_saver.ko -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sysinstall->Configure->Fdisk
sysinstall's 'FDISK Partition Editor' won't let me create a second slice. After pressing 'w' it says: "ERROR: Unable to write data to disk ad4!" then "Disk partition write returned an error status!" Freshly cvsup'd a few hours ago. # sysctl -a | grep kern.version kern.version: FreeBSD 5.0-CURRENT #2: Tue Feb 4 11:04:44 EST 2003 # fdisk ad4 *** Working on device ad4 *** parameters extracted from in-core disklabel are: cylinders=16708 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=16708 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 8388513 (4095 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 15/ sector 63 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: last KSE changes
On Tue, 28 Jan 2003 [EMAIL PROTECTED] wrote: > As for cross-arch breakage I suggest you run "make universe" before > committing in the future. > Does one have to be in "God-mode" to do this? :) (sorry...its a hot friday afternoon here) -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0-RC3 working great, but NOTES incomplete?
On Sun, 19 Jan 2003, Craig Reyenga wrote: > I got 5.0-RC3 working great on my box today, but when I went to make a > custom kernel and read NOTES i noticed that it makes no mention of > IPFIREWALL and friends. Is this intentional? > > craig@boss:~$ grep IPFIREWALL /sys/i386/conf/NOTES > craig@boss:~$ > > Nothing shows up. What's the scoop? > > -Craig > Confusing, huh. Read the top of the file again: # This file contains machine dependent kernel configuration notes. For # machine independent notes, look in /sys/conf/NOTES. -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: upgrading from STABLE to 5.0
[cc'd to -current where changes are made] On Mon, 20 Jan 2003, David Schultz wrote: > If you want to run binaries (e.g. ports) compiled for FreeBSD 4.X, > you need the option. If you don't, then you can remove it. > However, if you remove it, your old world may not work with the > new kernel. Therefore, at least for the initial 4.X->5.0 upgrade, > you should leave COMPAT_FREEBSD4 in the kernel config until you > have installed a new world. The option is *compulsary*!!!?!! (well, sort of...) sys/kern/kern_sig.c says: #if !defined(COMPAT_FREEBSD4) && !defined(NO_COMPAT_FREEBSD4) #error "You *really* want COMPAT_FREEBSD4 on -current for a while" #endif A buildworld will bomb if you don't have one of those options set. There is no mention of NO_COMPAT_FREEBSD4 anywhere. -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: some 5.0 oddities
> > > > 1/ Everytime I ssh to the box there are 4 connection attempts to UDP > > port 53 from itself. ie: > > > > Jan 18 12:45:17 team2 kernel: Connection attempt to UDP 172.22.2.12:53 >from 172.22.2.12:49205 > > Jan 18 12:45:17 team2 kernel: Connection attempt to UDP 172.22.2.12:53 >from 172.22.2.12:49206 > > Jan 18 12:45:17 team2 kernel: Connection attempt to UDP 172.22.2.12:53 >from 172.22.2.12:49207 > > Jan 18 12:45:17 team2 kernel: Connection attempt to UDP 172.22.2.12:53 >from 172.22.2.12:49208 > > > > I have log_in_vain="1" and /etc/resolv.conf points to 172.22.2.1 only. > > Is there any case 172.22.2.1 redirects DNS queries back to 172.22.2.22 > for some subdomain that it believes 172.22.2.22 is more fit to reply > for? What is the setup of 172.22.2.1? > No. 172.22.2.1 is authorative for 172.22.2/24 and will only forward requests upstream. > > 2/ The console doesn't "wake up" if its in screensaver mode (I use > > warp_saver.ko) when messages are sent to it (like the ones above). > > This is a result of th following sysctl: > > hw.syscons.saver.keybonly: 1 > > It defaults to 1 so you will have to edit your /etc/sysctl.conf and > set it to zero to enable the old behavior of syscons. > Thanks. One wonders why the old default behaviour was changed though... > > 3/ 'ps ul' repeats columns: PID, VSZ, RSS, TT, STAT, TIME, COMMAND > > (hmm, this also happens on 4.7) > > I'm not sure about this one. It seems to me that "ps l" prints a lot > of the information that "ps u" would print already. The repetition is > most likely a ps bug though. > Yes, its a bug - [EMAIL PROTECTED] has fixed it now. > > 4/ You can't interrupt the BTX loader anymore. Used to be able to > > get the ':' prompt before the kernel loaded. > > I regularly interrupt my loader at any stage. > Can you elaborate a bit on this one? > When 4.7 boots, the 'propeller' starts spinning, then momentarily stops. When you press a key, you get a ':' prompt. Otherwise it continues to load kernel. I'll have to reboot a box to fully explain, which I cant do right now... > > 5/ disklabel doesn't work: [...] > > ENOCLUE. > -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
some 5.0 oddities
Some of observations of 5.0-RELEASE: 1/ Everytime I ssh to the box there are 4 connection attempts to UDP port 53 from itself. ie: Jan 18 12:45:17 team2 kernel: Connection attempt to UDP 172.22.2.12:53 from 172.22.2.12:49205 Jan 18 12:45:17 team2 kernel: Connection attempt to UDP 172.22.2.12:53 from 172.22.2.12:49206 Jan 18 12:45:17 team2 kernel: Connection attempt to UDP 172.22.2.12:53 from 172.22.2.12:49207 Jan 18 12:45:17 team2 kernel: Connection attempt to UDP 172.22.2.12:53 from 172.22.2.12:49208 I have log_in_vain="1" and /etc/resolv.conf points to 172.22.2.1 only. 2/ The console doesn't "wake up" if its in screensaver mode (I use warp_saver.ko) when messages are sent to it (like the ones above). 3/ 'ps ul' repeats columns: PID, VSZ, RSS, TT, STAT, TIME, COMMAND (hmm, this also happens on 4.7) 4/ You can't interrupt the BTX loader anymore. Used to be able to get the ':' prompt before the kernel loaded. 5/ disklabel doesn't work: team2# disklabel ad4 disklabel: ioctl DIOCGDINFO: Operation not supported by device team2# disklabel -r ad4 disklabel: bad pack magic number (label is damaged, or pack is unlabeled) -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD 5.0 RC3 now available
On Tue, 14 Jan 2003, Trish Lynch wrote: > I just want to point out, POLA really only applies to -STABLE, and we're > talking very specifically about -CURRENT. > > IN -CURRENT, substantial changes can be made with little warning, and only > documentation sometimes (most of the time, people give a ***HEADS UP!*** > email on this list). > > However don;t assume because something is one way in the 4.x branch that > it will be the same in 5.x. If this were the case, we'd have very little > progress. > > -Trish > This makes sense, and I can live with it. I guess I'll have to 'forget' how FreeBSD has always done things in the past and relearn... Lots of things are very different - just this morning, I found out there is no 'visual configure'. Only took an hour to figure out why GENERIC was not finding the Adaptec 1542CF scsi card... While I'm here, dc(4) is still telling me its ethernet address is 00:00:00:00:00:00 and that there is 'no carrier'. It works fine otherwise. > > -- > Trish Lynch [EMAIL PROTECTED] > Ecartis Core Team [EMAIL PROTECTED] > EFNet IRC Operator @ efnet.demon.co.ukAilleCat@EFNet > Key fingerprint = C44E 8E63 6E3C 18BD 608F E004 9DC7 C2E9 0E24 DFBD > > -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD 5.0 RC3 now available
> > Le Monday 13 January 2003 18:22, Andy Farkas a écrit : French is such a sexy language... :) > indeed : > (see > ><http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/pkg_install/add/Makefile#rev1.15>) > Again, the acronym POLA springs to mind -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD 5.0 RC3 now available
> > > > Why does pkg_install now need libssl? > > > > troutmask:kargl[251] ldd /usr/sbin/pkg_add > /usr/sbin/pkg_add: > libfetch.so.3 => /usr/lib/libfetch.so.3 (0x28074000) > libmd.so.2 => /usr/lib/libmd.so.2 (0x2808) > libssl.so.2 => /usr/lib/libssl.so.2 (0x2808a000) > libcrypto.so.2 => /usr/lib/libcrypto.so.2 (0x280b9000) > libc.so.5 => /usr/lib/libc.so.5 (0x2817f000) > > I suspect your previous success in upgrading was accomplished > because the version number of libssl didn't change. Many of > the shared libraries in 5.0 have version number bumps, > including libssl.so.2. > > -- > Steve > FreeBSD 4.7-STABLE #1: Sat Jan 11 16:15:40 EST 2003: # ldd /usr/sbin/pkg_add /usr/sbin/pkg_add: libfetch.so.3 => /usr/lib/libfetch.so.3 (0x2806f000) libmd.so.2 => /usr/lib/libmd.so.2 (0x2807a000) libc.so.4 => /usr/lib/libc.so.4 (0x28083000) -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD 5.0 RC3 now available
> > Once again it's my pleasure to announce Release Cadidate 3 of > FreeBSD 5.0. Perhaps I do things in a non-standard way, but its worked for the last 8 years from 2.x through to 4.7-stable. Firstly, I download 'floppies' and create the 2 boot disks, kern.flp and mgsroot.flp. Then I download 'bin' (now called 'base'!?) to my fileserver. Next, I boot the box with 2 the new floppies, and tell sysinstall to use 'FTP' to the fileserver URL (ftp://172.22.2.2) and install 'minimal' (in other words, just install 'bin' (now called 'base'!? - anyone remember the acronym POLA?)). Sysinstall complains about not being able to find the 'crypto' stuff, but thats ok - its always done that. Next, I reboot the newly installed 'base' system, login as root, then 'shutdown now' to return back to network-enabled single user mode. Then I download 'cvsup-without-gui-16.1f.tgz' (into /root) and do a 'pkg_install cvsup-without-gui-16.1f.tgz' so I can cvsup the entire source tree onto the new box and do the make build{world,kernel} thing on the new box. No go for 5.0-RC3: # pkg_add cvsup-without-gui-16.1f.tgz /usr/libexec/ld-elf.so.1: Shared object "libssl.so.2" not found # Why does pkg_install now need libssl? -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
kernel compile bloat
Why does compiling a kernel (make buildkernel KERNCONF=GENERIC) take 7 times as much space on 5.0-current than it does on 4.7-stable? On a 4.7-stable box, /usr/obj/usr/src/sys totals 34 MB. On a 5.0-current box, /usr/obj/usr/src/sys totals 270 MB! (for each box, I rm /usr/obj/*, make buildworld, then make buildkernel KERNCONF=GENERIC) -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ia64 tinderbox failure
On Sun, 29 Dec 2002, Peter Wemm wrote: > ===> sbin/swapon > cc1: warnings being treated as errors > /home/tinderbox/ia64/src/sbin/swapon/swapon.c: In function `swaplist': > /home/tinderbox/ia64/src/sbin/swapon/swapon.c:246: warning: field width is not type >int (arg 3) > /home/tinderbox/ia64/src/sbin/swapon/swapon.c:246: warning: field width is not type >int (arg 5) > /home/tinderbox/ia64/src/sbin/swapon/swapon.c:265: warning: field width is not type >int (arg 3) > /home/tinderbox/ia64/src/sbin/swapon/swapon.c:265: warning: field width is not type >int (arg 5) > /home/tinderbox/ia64/src/sbin/swapon/swapon.c:274: warning: field width is not type >int (arg 2) > /home/tinderbox/ia64/src/sbin/swapon/swapon.c:274: warning: field width is not type >int (arg 4) > *** Error code 1 Is anybody gonna fix this? Or is it time to add a new procmail rule... -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GEOM panic
This fixes it, thanks. On Thu, 19 Dec 2002 [EMAIL PROTECTED] wrote: > Can you try this patch please ? > > Index: geom_mbr.c > === > RCS file: /home/ncvs/src/sys/geom/geom_mbr.c,v > retrieving revision 1.28 > diff -u -r1.28 geom_mbr.c > --- geom_mbr.c17 Dec 2002 09:44:10 - 1.28 > +++ geom_mbr.c19 Dec 2002 06:22:00 - > @@ -393,6 +397,7 @@ > g_mbr_print(1, dp + 1); > if ((dp[0].dp_flag & 0x7f) == 0 && >dp[0].dp_size != 0 && dp[0].dp_typ != 0) { > + g_topology_lock(); > g_slice_config(gp, slice, G_SLICE_CONFIG_SET, > (((off_t)dp[0].dp_start) << 9ULL) + off, > ((off_t)dp[0].dp_size) << 9ULL, > -- > 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 > -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
UPDATING error
$FreeBSD: src/UPDATING,v 1.228 2002/10/30 20:11:07 imp Exp $ "To upgrade from 4.x-stable to current" suggests: cd src/sys/boot ; make install [6] This does not work. You need to: cd src/sys/boot ; make all install [6] -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
dc(4) problems
I have a Macronix 98715A network adpater that works on RELEASE-4.6-p2 but not under very recent 5.0-CURRENT (same box). Under -current the ethernet address is set to 00:00:00:00:00:00 and a warning about sleeping with a lock set is emmitted. dmesgs: FreeBSD RELEASE-4.6-p2 #0: Sun Jul 14 22:29:30 GMT 2002 ... dc0: port 0xe800-0xe8ff mem 0xf3fff000-0xf3fff0ff irq 10 at device 7.0 on pci0 dc0: Ethernet address: 00:00:e8:89:ba:90 miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ... FreeBSD 5.0-CURRENT #0: Tue Nov 26 03:09:21 EST 2002 ... dc0: port 0xe800-0xe8ff mem 0xf3fff000-0xf3fff0ff irq 10 at device 7.0 on pci0 dc0: Ethernet address: 00:00:00:00:00:00 miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto /usr/src/sys/vm/uma_core.c:1330: could sleep with "dc0" locked from /usr/src/sys/pci/if_dc.c:1974 ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make.conf and make.conf(5)
On Tue, 19 Nov 2002, Carl Schmidt wrote: > The following PR has two patches attached which address the lack of some > documentation of make.conf in the manual page. It also contains a patch > for make.conf to fix style inconsistencies and two (if I recall > correctly) items which are documented in the manual page but did not > exist in the example conf. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=45470 > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=116926+0+current/freebsd-doc > -- > Carl Schmidt > Tom, please also consider this suggestion I made over two years ago: *Date: Fri, 13 Oct 2000 08:53:34 +1100 (EST) *From: Andy Farkas <[EMAIL PROTECTED]> *To: [EMAIL PROTECTED] *Subject: NOMAN I was trying to build a minimul system from sources and noticed that there is no mention of disabling the building and installing of man pages. Should the NOMAN knob be documented in both /etc/defaults/make.conf and /usr/src/Makefile.inc1 ? --- /usr/src/etc/defaults/make.conf-origMon Sep 25 19:08:01 2000 +++ /usr/src/etc/defaults/make.conf Fri Oct 13 08:33:17 2000 @@ -69,4 +69,5 @@ #NOINFO= true# do not make or install info files #NOLIBC_R= true# do not build libc_r (re-entrant version of libc) +#NOMAN=true# do not build and install man pages #NOPERL= true# To avoid building perl #NOPROFILE=true# Avoid compiling profiled libraries --- /usr/src/Makefile.inc1-orig Tue Oct 10 01:28:47 2000 +++ /usr/src/Makefile.inc1 Fri Oct 13 08:48:34 2000 @@ -13,4 +13,5 @@ # -DNOSHARE do not go into share subdir # -DNOINFO do not make or install info files +# -DNOMAN do not make or install man files # -DNOLIBC_R do not build libc_r. # -DNO_FORTRAN do not build g77 and related libraries. -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: rstat()
On Tue, 1 Oct 2002, Alfred Perlstein wrote: > Whoa :) > > I'm the RPC maintainer? > > Well ok, I've just checked in a fix for the prototypes being declared > into -current, I'll take a shot at -stable RSN (most likely tomorrow). > As far as a manpage I don't know when I'll have time for that. > > -- > -Alfred Perlstein [[EMAIL PROTECTED]] > 'Instead of asking why a piece of software is using "1970s technology," > start asking why software is ignoring 30 years of accumulated wisdom.' > The change you made to src/include/rpcsvc/rstat.x has broken a -current buildworld on a -stable box: ===> lib/librpcsvc cc -O -pipe -mcpu=pentiumpro -DYP -I/usr/obj/heffer/src/i386/usr/include/rpcsvc -c /heffer/src/lib/librpcsvc/rstat.c -o rstat.o /heffer/src/lib/librpcsvc/rstat.c:50: conflicting types for `rstat' /usr/obj/heffer/src/i386/usr/include/rpcsvc/rstat.h:87: previous declaration of `rstat' /heffer/src/lib/librpcsvc/rstat.c: In function `rstat': /heffer/src/lib/librpcsvc/rstat.c:55: warning: passing arg 5 of `callrpc' from incompatible pointer type /heffer/src/lib/librpcsvc/rstat.c:55: warning: passing arg 7 of `callrpc' from incompatible pointer type /heffer/src/lib/librpcsvc/rstat.c: In function `havedisk': /heffer/src/lib/librpcsvc/rstat.c:66: warning: passing arg 5 of `callrpc' from incompatible pointer type /heffer/src/lib/librpcsvc/rstat.c:66: warning: passing arg 7 of `callrpc' from incompatible pointer type *** Error code 1 Stop in /heffer/src/lib/librpcsvc. *** Error code 1 -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
buildworld fails
Trying to buildworld on a -stable box does this: -- >>> stage 2: build tools -- cd /heffer/src; MAKEOBJDIRPREFIX=/usr/obj DESTDIR= INSTALL="sh /heffer/src/tools/install.sh" make -f Makefile.inc1 -DBOOTSTRAPPING -DNO_CPU_CFLAGS build-tools make: no target to make. "/heffer/src/Makefile.inc1", line 140: warning: "make -f /dev/null -m /heffer/src/share/mk CPUTYPE=dummy -V CPUTYPE" returned non-zero status echo "===> bin/csh"; cd /heffer/src/bin/csh; make DIRPRFX=bin/csh/ build-tools ===> bin/csh echo "===> bin/sh"; cd /heffer/src/bin/sh; make DIRPRFX=bin/sh/ build-tools ===> bin/sh cc -O -pipe -DSHELL -I. -I/heffer/src/bin/sh -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wformat=2 -Wno-format-extra-args -Werror -D__FBSDID=__RCSID -c /heffer/src/bin/sh/mksyntax.c cc1: warnings being treated as errors /heffer/src/bin/sh/mksyntax.c: In function `digit_convert': /heffer/src/bin/sh/mksyntax.c:396: warning: unknown conversion type character `t' in format *** Error code 1 Stop in /heffer/src/bin/sh. *** Error code 1 Stop in /heffer/src. *** Error code 1 Stop in /heffer/src. *** Error code 1 Stop in /heffer/src. heffer# -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
space needed to compile GENERIC
How much disk space is required to compile a GENERIC 5.0-current kernel? I am attempting to upgrade from RELENG_4 to 5.0. On my (other) -stable box, du -s /usr/obj/usr/src/sys/GENERIC shows 34 meg. On the box I am upgrading, 'make buildkernel' bombed out when the disk filled up. /usr/obj/src/src/sys/GENERIC was over 192 meg !!! -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Another possible solution for non-sendmail users
On Thu, 28 Mar 2002, Gregory Neil Shapiro wrote: > In a somewhat unrelated note, I also plan on arranging to move the > sendmail-specific stuff out of src/etc/mail/ and into src/etc/sendmail so > the installation of things like sample sendmail maps, etc. don't clutter a > NO_SENDMAIL installation. I'll need to arrange this event with the CVS > repomeisters. Hopefully, this change (along with the patch) will make > things more palatable for non-sendmail users. Could you expand on this please? Why would a NO_SENDMAIL installworld install sendmail maps, etc. in the first place? It shouldn't matter what the source directory is. ps. not on -current atm (hence the xpost) - rectifying -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
On Thu, 30 Aug 2001, Bruce Evans wrote: > I've found acpica as useful as any other disk filling service and hope > it stays that way. > > Bruce Can someone put this in fortunes.dat :) -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IP wierdness...
> >tcpdump on the laptop sees the packet? That's very odd. > > Ceratinly is. I don't think this particular problem has anything > to do with the cardbus adapter. I run tcpdump with "-v -v -v" and > it never reported a bad checksum either. For curiosity's sake, I'd try a different cable to the hub... > > -- > Justin > -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
BSDcon Was: Re: current hangs when boot
On Tue, 24 Oct 2000, Warner Losh wrote: > We also found at bsdcon that lots of keystrokes would also make the > system boot. > > Warner For those of us that couldn't go, has anybody posted pictures from the con yet? ...any kind of pictures - not just ones of keyboard bashing... -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
NOMAN
I was trying to build a minimul (RELENG_4) system from sources and noticed that there is no mention of disabling the building and installing of man pages. Should the NOMAN knob be documented in both /etc/defaults/make.conf and /usr/src/Makefile.inc1 ? --- /usr/src/etc/defaults/make.conf-origMon Sep 25 19:08:01 2000 +++ /usr/src/etc/defaults/make.conf Fri Oct 13 08:33:17 2000 @@ -69,4 +69,5 @@ #NOINFO= true# do not make or install info files #NOLIBC_R= true# do not build libc_r (re-entrant version of libc) +#NOMAN=true# do not build and install man pages #NOPERL= true# To avoid building perl #NOPROFILE=true# Avoid compiling profiled libraries --- /usr/src/Makefile.inc1-orig Tue Oct 10 01:28:47 2000 +++ /usr/src/Makefile.inc1 Fri Oct 13 08:48:34 2000 @@ -13,4 +13,5 @@ # -DNOSHARE do not go into share subdir # -DNOINFO do not make or install info files +# -DNOMAN do not make or install man files # -DNOLIBC_R do not build libc_r. # -DNO_FORTRAN do not build g77 and related libraries. -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "fetch | sh" panics system
Did this on a: FreeBSD 4.0-STABLE #1: Fri May 26 06:47659 EST92000 system and got these messages in /var/log/messages: May 30 02:32:49 doohan /kernel: cmd conftest pid 12565 tried to use non-present SYSVSEM May 30 02:32:49 doohan /kernel: pid 12565 (conftest), uid 0: exited on signal 12 (core dumped) May 30 02:32:50 doohan /kernel: cmd conftest pid 12583 tried to use non-present SYSVSEM May 30 02:32:50 doohan /kernel: pid 12583 (conftest), uid 0: exited on signal 12 (core dumped) On Tue, 30 May 2000, Christian Weisgerber wrote: > Date: Tue, 30 May 2000 16:28:31 +0200 > From: Christian Weisgerber <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: "fetch | sh" panics system > > 5.0-CURRENT from ~May 17, dual ppro. > > The following, completely innocuous command line > > $ fetch -o - http://sites.inka.de/mips/unix/freebsd/xterm.shar | sh > > executed as a non-priviledged user, reproducibly panics the machine. > > - > #0 boot (howto=256) at ../../kern/kern_shutdown.c:303 > #1 0xc0163879 in panic (fmt=0xc028dc4f "page fault") > at ../../kern/kern_shutdown.c:553 > #2 0xc025760c in trap_fatal (frame=0xc8830d74, eva=52) > at ../../i386/i386/trap.c:927 > #3 0xc025727d in trap_pfault (frame=0xc8830d74, usermode=0, eva=52) > at ../../i386/i386/trap.c:820 > #4 0xc0256de3 in trap (frame={tf_fs = -930938856, tf_es = -1072103408, > tf_ds = -1062797296, tf_edi = -930935184, tf_esi = -930935300, > tf_ebp = -930935340, tf_isp = -930935392, tf_ebx = -931419456, > tf_edx = 0, tf_ecx = 13, tf_eax = -930935360, tf_trapno = 12, > tf_err = 0, tf_eip = -1062106920, tf_cs = 8, tf_eflags = 66195, > tf_esp = -930935360, tf_ss = -930935300}) at ../../i386/i386/trap.c:426 > #5 0xc0b188d8 in ?? () > #6 0xc0198fae in vn_open (ndp=0xc8830ec8, fmode=1026, cmode=420) > at vnode_if.h:305 > #7 0xc0195005 in open (p=0xc7df7a00, uap=0xc8830f80) > at ../../kern/vfs_syscalls.c:995 > #8 0xc025793d in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, > tf_edi = 8, tf_esi = 672168216, tf_ebp = -1077938468, > tf_isp = -930934828, tf_ebx = 672102756, tf_edx = 672168216, > tf_ecx = 15, tf_eax = 5, tf_trapno = 12, tf_err = 2, tf_eip = 672019108, > tf_cs = 31, tf_eflags = 663, tf_esp = -1077938512, tf_ss = 47}) > at ../../i386/i386/trap.c:1126 > #9 0xc024579e in Xint0x80_syscall () > > -- > Christian "naddy" Weisgerber [EMAIL PROTECTED] > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Scheduler changes?
On Mon, 29 May 2000, Bruce Evans wrote: > Scheduling was broken in -current on 2004/04/30 11:33:44 PDT. "nice -20" in > -current does essentially the same thing as "nice -10" in 4.0 (not enough > even in 4.0). hmmm... so there's a few years to wait before we have to worry.. :-) > > Bruce > > -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Breaking "build world" costs $5? (was: Can we please have acurrent that compiles?)
On Mon, 15 May 2000, Greg Lehey wrote: > >>>>> Maybe the comitters ought to take an idea from many software companies and > >>>>> contribute $5 to the beer fund every time they break the build. Have it > >>>>> all come due at the next BSDcon to fund a committer beer bash. :-) > >>> > >>> I think that we should make it $5.00 the first time. $10 the second > >>> time. $20 the third time, etc. > > > > Or perhaps we should tie it to the time it takes the security officer > > to fix... > > I think you're missing the point. The intention was the equivalent of > the pointy hat, just with the additional benefit that others might > have something out of it as well, no more. If the intention is derogatory, then perhaps an offender should be made to fix 5 PR's. Works around the underage drinking problem, too! :) > > Greg > -- > Finger [EMAIL PROTECTED] for PGP public key > See complete headers for address and phone numbers > -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP buildworld times / performance tests
On Wed, 29 Mar 2000, Matthew Dillon wrote: > time make -j 20 buildworldbuild FreeBSD-current using 4.0 kernel > > 4745.607u 1673.646s 1:29:07.45 120.0% 1323+1599k 8237+251565io 1615pf+0w > > time make -j 20 buildworldbuild FreeBSD-current using 5.0 kernel > > 4696.987u 1502.278s 1:10:34.17 146.4% 1359+1641k 10889+4270io 1779pf+0w Can I ask why is there a huge difference in the number of io (251k vs 4k)? What is so different between 4.0 and 5.0 that causes this? -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! old wd driver going away
Damn. I'm gonna miss my faithful, old (circa 1993), worksation (dual P90, Intel Neptune based PCI+EISA), with a crappy "TEKRAM DC-6X0X IDE cacheing controller" in it. Been using this thing since 3.0-current when SMP was first introduced...(it was previously running OS/2 2.1 SMP) Fortunately, I can switch to using a SCSI disk on my DPT PM2022 EISA card, which is now supported - but only with 1 disk! (the driver does not work with a LUN != 0) > Yes... > > That's right. > > Use ata and related stuff instead. > > -- > Jeroen Ruigrok van der Werven Network- and systemadministrator > <[EMAIL PROTECTED]> VIA NET.WORKS The Netherlands > BSD: Technical excellence at its best http://www.bart.nl > In my Dreams, I see you, I can tell you, how I feel... > -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
adduser(8) removes comments from /etc/group - was: Re: minor nitwith 4.0-RC2
On Tue, 22 Feb 2000, Jeffrey J. Mountin wrote: > >I'm not sure I understand this - sysinstall doesn't install an > >/etc/group file so there's really no "sysinstall version" which is > >distinct from that installed as part of the bindist, at least to my > >knowledge. > > Nevermind. > > Manually extracted etc/group and it has the tag line. > > Must/might be losing it, but then I don't strip the tag lines when I edit > files. 8-/ > > Then again maybe adduser does this. Could start fresh again I suppose and > see what went wrong or if I lose my pilots license. > adduser(8) will remove any comments from /etc/group, including the $FreeBSD tag. Does sysinstall call adduser? -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-RC -- /etc/rc, NFS, & nis_client_enable="NO"
Seems like a good idea to me not to have a message displayed if explicitly configured not to do something! If you have `nfs_enable_client="NO"' and if you have nfs mounts in your fstab, then this could be a method of delaying those mounts until after boot/init time? On Mon, 14 Feb 2000, David Wolfskill wrote: > I discovered this under 3.4-R, and checked that it's still the case > for 4.0-RC. > > I'm putting together a box that has no reason whatsoever to use or > provide any NFS services at all. > > It was thus with a sense of "POLA violation" that I happened across the > message > > Mounting NFS file systems > > in the boot-up messages. > > > Turns out that the stanza that generates that (in /etc/rc) looks like: > > echo -n "Mounting NFS file systems" > mount -a -t nfs > echo . > > ...as in, this isn't conditional on anything. > > OK; fine. Maybe I'm not a programmer (any more), but this seems to > work OK: > > -%< > > --- rcTue Feb 8 22:32:40 2000 > +++ /tmp/rc Mon Feb 14 14:11:01 2000 > @@ -191,9 +191,14 @@ > network_pass1 > fi > > -# Mount NFS filesystems. > -echo -n "Mounting NFS file systems" > -mount -a -t nfs > +case ${nfs_client_enable} in > +[Yy][Ee][Ss]) > + # Mount NFS filesystems. > + echo -n "Mounting NFS file systems" > + mount -a -t nfs > + ;; > +esac > + > echo . > > # Whack the pty perms back into shape. > > ->% > > Downside is that it's possible that there are machines that actually *do* > act as NFS clients, even though nfs_client_enable is not set affirmatively. > Then again, it could be argued that a new release would be one of the > better times to make this kind of change, eh...? :-) > > (I'd do a send-pr, but I don't actually have a 4.0-RC system running at > the moment, and I need to get this system running ASAP; the above was > based on a 4.0-RC filesystem that is accessible from another machine, and > I actually did the equivalent patch to the 3.4-R system, which survived the > experiment... though, as noted, it doesn't use NFS.) > > Cheers, > david > -- > David Wolfskill [EMAIL PROTECTED] UNIX System Administrator > voice: (650) 577-7158 pager: (888) 347-0197 FAX: (650) 372-5915 > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Unknown PCI card
Are there any plans for the Initio INI-A100U2W PCI SCSI controller cards? You can get driver source code for FreeBSD from http://www.initio.com/ -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
vidcontrol is not working properly
Maybe something broke with the "3rd stage of syscons code reorganization". I'm sure this worked properly around the end of December last year. I don't know when exactly it stopped working. $ vidcontrol -r black green VGA_80x60 green black does not set the reverse colours. $ vidcontrol -r black green does. This is happening on -current cvsup'd and built Jan 26, 2000. -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAIN
> What's the current wuildworld times for a 486DX2-66 + 12M RAM over > NFS? I have a small box that I'd like to torture test before putting > into service and thought this would make a good week long test. 'torture test' is an understatement. This was a 'buildworld' of 3.4-stable, on 486DX2-66 with 32MB RAM, and both src and obj on the same local disk (softupdates enabled): Script started on Thu Jan 20 01:01:00 2000 backup# cd /usr/src backup# /usr/bin/time make buildworld -- >>> Cleaning up the temporary elf build tree -- mkdir -p /usr/obj/citus/src/tmp chflags -R noschg /usr/obj/citus/src/tmp/ rm -rf /usr/obj/citus/src/tmp ... gzip -cn /citus/src/usr.sbin/wlconfig/wlconfig.8 > wlconfig.8.gz ===> etc ===> etc/sendmail rm -f freebsd.cf (cd /citus/src/etc/sendmail && m4 -D_CF_DIR_=/citus/src/etc/sendmail/../../contrib/sendmail/cf/ /citus/src/etc/sendmail/../../contrib/sendmail/cf/m4/cf.m4 freebsd.mc) > freebsd.cf chmod 444 freebsd.cf 54172.61 real 39360.42 user 6506.89 sys backup# Script done on Thu Jan 20 16:22:31 2000 > > Warner > -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ascii art in hosts.allow
On Wed, 26 Jan 2000, Sheldon Hearn wrote: > > Change it to hosts.allow.sample then? No hosts.allow file is essentially > > the same as the ALL:ALL:allow rule, no? > > No. In the absence of a hosts.allow file, hosts_access(3) denies all. Not according to what I read in 'man 5 hosts_access' - especially the second paragraph titled "ACCESS CONTROL FILES". > > Can we please move onto something else now. :-) > But...but... ITS SUCH AN EYE-SORE IMHO. > Ciao, > Sheldon. > -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: y2k problem? naahhh...
On Tue, 25 Jan 2000, John Baldwin wrote: > >> Backup passwd and group files: > >> passwd diffs: > >> --- /var/backups/master.passwd.bak Wed Jan 5 10:(password):41 2000 > >> +++ /etc/master.passwd Tue Jan 25 15:(password):44 2000 > >> @@ -1,3 +1,5 @@ > >> +# $FreeBSD:(password):09:07 peter Exp $ > >> +# > >> root:(password):0:0::0:0:Charlie &:/root:/bin/csh > >> toor:(password):0:0::0:0:Bourne-again Superuser:/root: > >> daemon:(password):1:1::0:0:Owner of many system > >> processes:/root:/sbin/nologin > > > > Heh, I'd say revision 1.5 of "src/etc/periodic/daily/200.backup-passwd" > > needs a bit more work. :-) > > Doh, I tried to fix the sed expression so it would work with various diff > formats (since I, for example, prefer the old format). I guess a simple: > 'egrep -v '^(---|+++|@@)' inserted in the pipeline between the diff -u and the > sed might fix it. The $FreeBSD ID is being creamed as well. > > > John > > -- > > John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
y2k problem? naahhh...
There are some pretty funky date/times being displayed in my daily run output. Just thought I'd mention it; I've only just upgraded to 4.0-current and don't recall seeing this before. Backup passwd and group files: passwd diffs: --- /var/backups/master.passwd.bak Wed Jan 5 10:(password):41 2000 +++ /etc/master.passwd Tue Jan 25 15:(password):44 2000 @@ -1,3 +1,5 @@ +# $FreeBSD:(password):09:07 peter Exp $ +# root:(password):0:0::0:0:Charlie &:/root:/bin/csh toor:(password):0:0::0:0:Bourne-again Superuser:/root: daemon:(password):1:1::0:0:Owner of many system processes:/root:/sbin/nologin -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ascii art in hosts.allow
On Mon, 24 Jan 2000, David O'Brien wrote: > > What is the reason for putting a giant "Example!" in hosts.allow? > > So you'll notice that this file is an example and *demands* your > attention in configuring your system properly. Change it to hosts.allow.sample then? No hosts.allow file is essentially the same as the ALL:ALL:allow rule, no? > > I note that it was committed at 3 o'clock in the morning... > > Sounds like normal hacking time to me. Fair enough. Please note that I respect your efforts, and was not trying to insinuate anything. I just find this kind of [ascii art] thing a bit out of style with the rest of the system. This is the point I'm trying to make. > > was someone trying to make a point? > > Yes, don't shoot yourself in the foot by leaving your system wide open. Then say this in a new comment at the top of the file. It is not clear *why* you have to modify it, although the next set of comments does say "Start by allowing everything". It works out-of-the-box, so why should you change it? (yes, I know why). > > What other files have this type of gross bit-bloat in them? > > src/sys/ Again, what I was trying to say is that there aren't any other files with giant lettering in them, are there? > > -- > -- David([EMAIL PROTECTED]) > -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ascii art in hosts.allow
What is the reason for putting a giant "Example!" in hosts.allow? I note that it was committed at 3 o'clock in the morning... was someone trying to make a point? What other files have this type of gross bit-bloat in them? Here is a patch: (please notice the spelling correction) --- hosts.allow.origTue Jan 25 14:53:05 2000 +++ hosts.allow Tue Jan 25 14:56:45 2000 @@ -2,20 +2,14 @@ # hosts.allow access control file for "tcp wrapped" apps. # $FreeBSD: src/etc/hosts.allow,v 1.6 1999/11/25 03:00:44 obrien Exp $ # -# NOTE: The hosts.deny file is not longer used. Instead, put both 'allow' +# NOTE: This is an example file only. You will need to modify it for your +# specific requirements. + +# NOTE: The hosts.deny file is no longer used. Instead, put both 'allow' # and 'deny' rules in the hosts.allow file. + # see hosts_options(5) for the format of this file. # hosts_access(5) no longer fully applies. - -# _ _ _ -# | | __ __ __ _ _ __ ____ __ | | ___ | | -# | _| \ \/ / / _` | | '_ ` _ \ | '_ \ | | / _ \ | | -# | |___ > < | (_| | | | | | | | | |_) | | | | __/ |_| -# |_| /_/\_\ \__,_| |_| |_| |_| | .__/ |_| \___| (_) -# |_| -# !!! This is an example! You will need to modify it for your specific -# !!! requirements! - # Start by allowing everything (this prevents the rest of the file # from working, so remove it when you need protection). -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvsup 3.4-release to -current
On Thu, 20 Jan 2000, f.johan.beisser wrote: > that's very accurate. you'd be better off getting a SNAP image and > upgrading your system from that. > > that is, if you really need to do it now. > > i'd just wait, untill the final release, since it's coming up Real Soon > Now. > > -- jan > > On Thu, 20 Jan 2000, Matt M. wrote: > > > Just wondering what potential problems I am facing by going from > > 3.4-release to -current. I was told on irc that my chances may not be > > well. > > > > +-// f. johan beisser //--+ > email: jan[at]caustic.org web: http://www.caustic.org/~jan >"knowledge is power. power corrupts. study hard, be evil." Um, I thought we were supposed to be testing 4.0-current _before_ it goes -release... I am going to upgrade my workstation (from 3.4 to 4.0) over this weekend, to help further the cause... -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Solved(?): crash with ffs_softdep.c 1.52
On Mon, 17 Jan 2000, Alex Zepeda wrote: > Alexander Leidinger wrote: > > > I've successfully booted with ffs_softdep.c 1.54, I'm doing now a full > > buildworld to stress the system. > > Hmm. I still got repeatable crashes with 1.54, and finally got to the > point where lost+found got populated. I also just got my finger smashed > in a door, making writing a tad bit impossible. When the swelling/pain > goes down, I'll have a back trace :) Could you please explain why you need to smash a finger in a door in order to get a back trace?? What other grievous bodily harm does one need to inflict on one's self when kernel debugging? I know about hitting yourself on the head with a 4x2, but that only works for userland... These requirements should be mentioned in Section 22 of the Handbook. > > - alex > > ps. hope your finger is alright... :) -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
mergemaster(8) busted
After cvsup'ing, a -current system based on userland/kernel dated 31-dec-1999, 'mergemaster -sv' is failing with mknod errors. cd src/sbin/mknod ; make all install ; make clean fixes it. -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc compile error
On Tue, 28 Dec 1999, David O'Brien wrote: > > Perhaps a later snapshot of gcc will work . > > GCC 2.95.2 is a *RELEASED* version. We don't use snapshots as the base > compiler. What every the problem is 4.0 will live with it unless someone > narrows down the problem more. The latest Polygraph (ver 2.2.8) proxy-cache benchmarking source (Available at http://www.ircache.net/Polygraph/) does not compile on my very recent 4.0 system. (rebuilding world now...) I get this error, after dl'ing polygraph-2.2.8-src.tar.gz, running 'configure', then running 'make': ... c++ -g -O3 -Wall -Wwrite-strings -Woverloaded-virtual -Iinclude -Ixstd/include -Ipgl/include -Ixparser/include -I.. -DHAVE_CONFIG_H -c Connection.cc In file included from include/PortMgr.h:29, from Connection.cc:33: include/LevelStat.h:55: invalid type `const char[1]' for default argument to `const String &' *** Error code 1 Stop in /usr/home/andyf/src/polygraph/src. *** Error code 1 Stop in /usr/home/andyf/src/polygraph. The "offending" code looks like this: ostream &print(ostream &os, const String &pfx = "") const; When I did a 'touch Connection.o ; make' it compiled another source file that included PortMgr.h / LevelStat.h just fine, but bombed out elsewhere! > > -- > -- David([EMAIL PROTECTED]) > -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: shell pipeline bug
> Simplified example: > > sh -c "jot 6000 | cat | head" Not knowing what jot(1) was, I read the man page. The synopsis says: SYNOPSIS jot [-cnr] [-b word] [-w word] [-s string] [-p precision] [reps [begin ^ [end [s ^ ...so I type in: $ jot usage: jot [-cnr] [-b word] [-w word] [-s string] [-p precision] [reps [begin [end [s ^ ^ Is my understanding correct that options in square brackets are optional? -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
scsi tape driver wants an update
Just a reminder I guess, # uname -v FreeBSD 4.0-CURRENT #0: Sun Oct 10 16:16:34 EST 1999 # mt retension console emits (in bright white): WARNING: driver sa should register devices with make_dev() (dev_t = "#sa/1") -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gnu tar upgrade?
> Upgrading tar is something I've been wanting to do for over a > year. Anything to speed me along would be helpful. > Well, like the README file in src/gnu/usr.bin/tar says: "This GNU tar 1.11.2. Please send bug reports, etc., to [EMAIL PROTECTED] This is a beta-test release. Please ^^^ try it out. There is no manual; the release of version 1.12 will contain a manual." [the file is dated Jun 18, 1993!] Doesn't give one much confidence in the quality of the software, especially if you don't know its been heavily modified... Also, our tar has never been compatible with Amanda-2.41p1 (one must install gnu-tar 1.12 + patches). -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vty3 and 4.0 snap 080799
On Wed, 11 Aug 1999, Larry Lile wrote: > Use alt-F4 for the shell during install. > > vty0 -> alt-F1 [Install] > vty1 -> alt-F2 [Debug] > vty2 -> alt-f3 [Inactive] How about we emit a message: "This screen intentionally left blank." :) > vty3 -> alt-F4 [Shell] > > PrtScr will cycle through all available vty's. > > HTH. HAND :) > > Larry Lile > [EMAIL PROTECTED] > -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: installing hack(6) overwrites /var/games/hackdir/record file!
On Wed, 11 Aug 1999, Bob Bishop wrote: > >> Can anyone explain why every time I upgrade world, my hard earned 'record' > >> file whilst playing hack(6) gets overwritten by /dev/null, and also all > >> the user 'bones' and 'save' files rm'd? > > > >Blimey! I wondered where all my rogue(6) scores were going. This is an > >excellent idea. I'll submit a PR, with your diffs and some for rogue. > > I think you'll find that hack(6) itself silently removes save and bones > files that are older than the binary, a precaution because it relies on > data layout in the file. This is a PITA but nontrivial to fix. Yes, hack will invalidate any save or bones file that is older than the mtime of (hard coded!) "/usr/games/hide/hack". And it tells you about it. But I can live with that. Its the trashing of the 'record' file that I'm most concerned about. If this file was untouched during upgrades, I'd be happy. The other point is that the data layout hasn't changed since the game was first brought into the tree (circa Sep '94). > > -- > Bob Bishop+44 118 977 4017 > [EMAIL PROTECTED] fax +44 118 989 4254 (0800-1800 UK) > -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
installing hack(6) overwrites /var/games/hackdir/record file!
Perhaps this should be a PR... Seeing as how we are recently being amused by fortune(6) quotes, I thought I'd mention an acronymn that hasn't been used recently: POLA Can anyone explain why every time I upgrade world, my hard earned 'record' file whilst playing hack(6) gets overwritten by /dev/null, and also all the user 'bones' and 'save' files rm'd? If the interface to these files changes, surely the game should recognise it? I propose the following patch to src/games/hack: $ diff -u Makefile.orig Makefile --- Makefile.orig Wed Aug 11 04:16:06 1999 +++ MakefileWed Aug 11 04:16:20 1999 @@ -31,14 +31,14 @@ beforeinstall: ${INSTALL} -c -o ${BINOWN} -g ${BINGRP} -m ${NOBINMODE} /dev/null \ ${DESTDIR}/var/games/hackdir/perm +.if !exists(${DESTDIR}/var/games/hackdir/record) ${INSTALL} -c -o ${BINOWN} -g ${BINGRP} -m 460 /dev/null \ ${DESTDIR}/var/games/hackdir/record +.endif ${INSTALL} -c -o ${BINOWN} -g ${BINGRP} -m 440 ${.CURDIR}/rumors \ ${DESTDIR}/var/games/hackdir/rumors ${INSTALL} -c -o ${BINOWN} -g ${BINGRP} -m ${NOBINMODE} \ ${.CURDIR}/help ${.CURDIR}/hh ${.CURDIR}/data \ ${DESTDIR}/var/games/hackdir - rm -f ${DESTDIR}/var/games/hackdir/bones* \ - ${DESTDIR}/var/games/hackdir/save/* .include -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make world failure mode
On Mon, 3 May 1999, Bruce Evans wrote: > >I have noticed that if you do not have /usr/share/groff_font > >directory, a buildworld will fail. I think GROFF_FONT_PATH is > >missing from a Makefile maybe? The dev* directories are already > >built in the obj tree... > > Similarly for /usr/share/tmac and GROFF_TMAC_PATH. > > Not quite similarly for /usr/share/dict/{various}. groff uses these, > but there doesn't seem to be any macros for them. Hopefully they aren't > used by buildworld. A 'make buildworld' completed ok without a /usr/share/dict > > Bruce > -- :{ an...@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
make world failure mode
# uname -v FreeBSD 3.1-STABLE #2: Mon Apr 26 22:46:11 EST 1999 I have noticed that if you do not have /usr/share/groff_font directory, a buildworld will fail. I think GROFF_FONT_PATH is missing from a Makefile maybe? The dev* directories are already built in the obj tree... Script started on Sun May 2 15:28:26 1999 # make buildworld ===> share/doc/usd/13.viref sed -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(vi.ref\)$:\1/home/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(ex.cmd.roff\)$:\1/home/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(ref.so\)$:\1/home/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(set.opt.roff\)$:\1/home/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(vi.cmd.roff\)$:\1/home/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e 's:^\.so index.so$::' /home/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/vi.ref | groff -mtty-char -Tascii -t -s -me -o1- > /dev/null groff: can't find `DESC' file groff:fatal error: invalid device `ascii' *** Error code 3 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. # ^Dexit Script done on Sun May 2 17:12:14 1999 -- :{ an...@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: solid NFS patch #6 avail for -current - need testers files)
On Thu, 22 Apr 1999, Daniel Eischen wrote: > I have to echo these feelings. NFS, as both server and client, is > working without noticeable problems for us under the old 2.2-stable. > I am afraid of upgrading to 3.1-stable with the reported NFS problems, > and we can't get by without NFS. I was refering to the find/grep problem - I tried to start a thread in sta...@freebsd.org... > Dan Eischen > eisc...@vigrid.com > > -- :{ an...@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: solid NFS patch #6 avail for -current - need testers files)
> >:Just wondering if these changes also have the side effect of fixing the > >:nmap problem that crashes 3.x boxes ? i.e. as you wrote back on 3/4/99 > >: > >:>The problem is a deadlock caused by the fgrep. The fgrep is mmap()ing > >:>the file, but then it does some really weird crap when dealing with > >:>larger files. > >:> > >I believe this was fixed in -current. I don't know if it was backported > >to -stable. > > Unfortunately no... It can still lockup a 3.x machine. > This is the only thing stopping me from upgrading our production machines to 3.1-STABLE. Please, please, please backport these fixes! -- :{ an...@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message