Re: regex(3)
Alfred Perlstein wrote: * Daniel C. Sobral [EMAIL PROTECTED] [000709 12:46] wrote: I think all bugs with the performance improvements to regex(3) have all been solved now. I haven't heard of any problems for over a week about the first improvement (Boyer-Moore search), and I have now tested the code against the original test suit for Spencer's library. I'd like, thus, to merge the changes. If anyone have objections, please raise them now. :-) None other than waiting at least 2 weeks, or for 4.1 to come out. The idea was having those improvement on 4.1, of course. So I'll take this as an objection. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] jkh _DES: The Book of Bruce has only one sentence in it, and it says "the actual directives of my cult are left as an exercise for the reader. Good luck." EE jkh: does it really include the 'good luck' part? jkh EE: OK, I made that part up. jkh EE: I figured it should sound a bit more cheery than how Bruce initially dictated it to me. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0-20000706-SNAP boot floppy failure
In message [EMAIL PROTECTED], Jim Bloom writes: This may or may not be related... A week ago, I tried to boot using the 0702 snapshot floppies and had problems as well. The error I received was something like "Can't open md1". This was after probing all of the devices, but before the install menu came up. That has been fixed. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | 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
Re: HEADS UP! Always use the 'make buildkernel' target to make yerkernels (fwd)
I don't particularly want to be drawn into this whole buildfoo
bootstrapping thing..any other takers? :-)
Kris
--
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe [EMAIL PROTECTED]
-- Forwarded message --
Date: Mon, 10 Jul 2000 09:35:19 +0200
From: Udo Schweigert [EMAIL PROTECTED]
To: Kris Kennaway [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: HEADS UP! Always use the 'make buildkernel' target to make yer
kernels
On Sun, Jul 09, 2000 at 20:49:50 -0700, Kris Kennaway wrote:
Subject basically says it all. "make buildkernel KERNEL=whatever" and
"make installkernel KERNEL=whatever" (or set KERNEL in /etc/make.conf or
the environment, where KERNEL is the name of the kernel to build (GENERIC,
etc)) are what you should always be using to build your kernels, unless
you know what you're doing.
I found it was a good idea (by experience), to always have an up to date
version of the GENERIC-kernel available in /. Since it is possible to
build two kernel by saying
# make buildkernel KERNEL="mykernel GENERIC"
it would also be nice to have the possibility to install both new kernels to
/ (instead of only installing the first) by saying
# make installkernel KERNEL="mykernel GENERIC"
Attached you find a patch to do this.
Best regards.
--
Udo Schweigert, Siemens AG | Voice : +49 89 636 42170
ZT IK 3, Siemens CERT| Fax: +49 89 636 41166
D-81730 Muenchen / Germany | email : [EMAIL PROTECTED]
PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2
--- Makefile.inc1.orig Sun Jul 2 13:00:19 2000
+++ Makefile.inc1 Mon Jul 10 09:25:36 2000
@@ -356,13 +356,11 @@
.endif
BUILDKERNELS=
-INSTALLKERNEL=
+INSTALLKERNELS=
.for _kernel in ${KERNEL}
.if exists(${KRNLCONFDIR}/${_kernel})
BUILDKERNELS+= ${_kernel}
-.if empty(INSTALLKERNEL)
-INSTALLKERNEL= ${_kernel}
-.endif
+INSTALLKERNELS+= ${_kernel}
.endif
.endfor
@@ -393,12 +391,14 @@
#
# installkernel
#
-# Install the kernel defined by INSTALLKERNEL
+# Install the kernels defined by INSTALLKERNELS
#
installkernel:
- cd ${KRNLOBJDIR}/${INSTALLKERNEL}; \
- ${IMAKEENV} MACHINE=${MACHINE} KERNEL=${INSTALLKERNEL} \
+.for _kernel in ${INSTALLKERNELS}
+ cd ${KRNLOBJDIR}/${_kernel}; \
+ ${IMAKEENV} MACHINE=${MACHINE} KERNEL=${_kernel} \
${MAKE} install
+.endfor
#
# update
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! Always use the 'make buildkernel' target to make yer kernels (fwd)
Hi all, Please have a look at the patch in PR 17698 http://www.freebsd.org/cgi/query-pr.cgi?pr=17698 It deal with this problem. /K To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Multiple free panic on SMP
On Sun, 9 Jul 2000, Ollivier Robert wrote: After updating to the very latest current code, I get a multiple free panic on my SMP machine. It always happen during buildworld in libc_r. Important note : I have the snapshot code from Kirk. The panic is in random_read which does a free. Here is the trace. This should be fixed it rev.1.7 of randomdev.c. ... (kgdb) up #11 0xc0144340 in random_read (dev=0xc031e3c8, uio=0xc667bed8, flag=131072) at ../../dev/randomdev/randomdev.c:100 warning: Source file is more recent than executable. 100 ret = read_random(random_buf, c); (kgdb) list 95 void *random_buf; Source file has the fix :-). Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
panic
I get easily reproducable panics (supervisor read, page not present) in today's -CURRENT; yesterday's sources with the same config works fine. The kernel panics almost immediately if I run something that does a lot of writing to disk, such as a kernel or port build. It refuses to dump (dump already in progress) and I don't have a serial console handy for DDB, so no dump or backtrace, though according to nm(1) the page fault occurs in xpt_release_devq() in aic7xxx.c. I've attached the kernel config and the output of dmesg (from the kernel that works, not the one that panics). # # Kernel configuration for md5.follo.net # machine i386 cpu I586_CPU ident MD5 maxusers64 # Debugging options DDB options KTRACE # Networking options INET #optionsIPFIREWALL, IPFIREWALL_VERBOSE # File system options FFS, FFS_ROOT, SOFTUPDATES options PROCFS # XFree86 support options SYSVMSG, SYSVSEM, SYSVSHM options UCONSOLE # Misc. kernel options options AUTO_EOI_1, AUTO_EOI_2 options COMPAT_43 options INCLUDE_CONFIG_FILE options RANDOMDEV # POSIX real-time extensions options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L config kernel # Buses device isa device pci device apm # Numeric processor extensions device npx # Floppy controller device fdc # ATAPI controllers device ata device atadisk # SCSI controllers device ahc device scbus options SCSI_DELAY=2000 device pass device da device sa options SA_SPACE_TIMEOUT="(4*60)" device cd # System console and mouse device atkbdc device atkbd #device psm device vga device sc 1 options SC_DFLT_FONT makeoptions SC_DFLT_FONT=iso options SC_PIXEL_MODE options SC_HISTORY_SIZE=1024 device splash options VESA # I/O ports device sio device sio device ppc # PPBus devices device ppbus device lpt device plip device ppi # Network adapters #device miibus #device fxp # TeleS S0/16.3 passive ISDN adapter options TEL_S0_16_3 device isic # ISDN protocol stack device "i4bq921" device "i4bq931" device "i4b" # ISDN devices device "i4btrc"4 device "i4bctl" device "i4brbch" 4 device "i4btel"2 # Networking pseudo-devices device loop2 device ether device tun device bpf # Other pseudo-devices device pty device vn # Audio codec device pcm device sbc Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #30: Sun Jul 9 22:44:49 CEST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/MD5 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P54C (166.19-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x1bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8 real memory = 134217728 (131072K bytes) avail memory = 127635456 (124644K bytes) Preloaded elf kernel "kernel.works" at 0xc02cc000. Intel Pentium detected, installing workaround for F00F bug VESA: v2.0, 2304k memory, flags:0x0, mode table:0xc0274d42 (122) VESA: Tseng Labs ET6000 npx0: math processor on motherboard npx0: INT 16 interface apm0: APM BIOS on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 pci0: Intel 82439HX PCI cache memory controller at 0.0 isab0: Intel 82371SB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX3 ATA controller port 0xe800-0xe80f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 pci0: Tseng Labs ET6000/ET6100 graphics accelerator at 9.0 irq 9 pci0: unknown card (vendor=0x8086, dev=0x1229) at 10.0 irq 9 pci0: unknown card (vendor=0x1274, dev=0x1371) at 11.0 irq 12 ahc0: Adaptec 2940 Ultra SCSI adapter port 0xd000-0xd0ff mem 0xf800-0xf8000fff irq 11 at device 12.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 isic0 at port 0xd80-0xd9f,0x980-0x99f,0x180-0x19f,0x580-0x59f irq 5 flags 0x3 on isa0 isic0: Teles S0/16.3 ppc0: Parallel port at
Re: etc/rc.d things...
Kelly Yancey wrote: On Sat, 8 Jul 2000, Mike Meyer wrote: By all means, use start/stop args, but hard link the .sh files into seperate directories or something so that the order can be tweaked.. If all you want is to make sure that shutdown happens in the reverse order of startup, that can be done by reversing the list in rc.shutdown. But how about going a step further, and starting towards a user-friendly configuration process? Instead of being globbed at init time, etc/rc.d is a repository for things that take start/stop arguments. They are symlinked to /etc/init.d with numeric prefixes to control order at initialization time. Likewise, they can be symlinked to /etc/down.d (or shutdown.d) with numeric prefixes to control order at shutdown time. How about rather then separate directories, you prefix the symlink names with 'S' for startup scripts and 'K' (for "kill") for shutdown scripts. Then, you rename rc.d to rc3.d... I like it. It's clean and simple, almost to the point of being elegant. But why bother adding rc?.d if you are going to right it to handle s or k then the present home should be fine, no? Ducks and runs, Kelly -- Kelly Yancey - [EMAIL PROTECTED] - Belmont, CA System Administrator, eGroups.com http://www.egroups.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Cheers, Mikel +~+ | Optimized Computer Solutions, Inchttp://www.ocsny.com | 39 W14th Street, Suite 203 212 727 2238 x132 | New York, NY 10011 +~+ begin:vcard n:King;Mikel tel;fax:2124638402 tel;home:http://www.upan.org tel;work:2127272100 x-mozilla-html:TRUE org:Optimized Computer Solutions version:2.1 email;internet:[EMAIL PROTECTED] title:Director of Network Operations Technology adr;quoted-printable:;;39 W14th St.=0D=0ASte 203;New York;NY;10011;US note;quoted-printable:fBSD, PHP, MySql and OCS Rule!!!=0D=0A=0D=0AGoal is to be MS free by the end of 2k. x-mozilla-cpt:;7312 fn:Mikel King end:vcard
Closing kern/18019
Hi, could someone please close kern/18019 since it was solved some time ago. Bye/2 -- Michael Reifenberger - IT, UNIX, R/3-Basis Work: [EMAIL PROTECTED]Proj: [EMAIL PROTECTED] Pers: [EMAIL PROTECTED] Webspace: http://www.reifenberger.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: etc/rc.d things...
Please Please Please _Dont_!!! I dont know if someone is yoking, my english is not up to that :( I tried to secure a Solaris machine and hated the whole setup. I't have some good things but i take the simple rc.conf mechanism every time! /Johan On Mon, 10 Jul 2000, Mikel wrote: Kelly Yancey wrote: On Sat, 8 Jul 2000, Mike Meyer wrote: By all means, use start/stop args, but hard link the .sh files into seperate directories or something so that the order can be tweaked.. If all you want is to make sure that shutdown happens in the reverse order of startup, that can be done by reversing the list in rc.shutdown. But how about going a step further, and starting towards a user-friendly configuration process? Instead of being globbed at init time, etc/rc.d is a repository for things that take start/stop arguments. They are symlinked to /etc/init.d with numeric prefixes to control order at initialization time. Likewise, they can be symlinked to /etc/down.d (or shutdown.d) with numeric prefixes to control order at shutdown time. How about rather then separate directories, you prefix the symlink names with 'S' for startup scripts and 'K' (for "kill") for shutdown scripts. Then, you rename rc.d to rc3.d... I like it. It's clean and simple, almost to the point of being elegant. But why bother adding rc?.d if you are going to right it to handle s or k then the present home should be fine, no? Ducks and runs, Kelly -- Kelly Yancey - [EMAIL PROTECTED] - Belmont, CA System Administrator, eGroups.com http://www.egroups.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Cheers, Mikel +~+ | Optimized Computer Solutions, Inchttp://www.ocsny.com | 39 W14th Street, Suite 203 212 727 2238 x132 | New York, NY 10011 +~+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: etc/rc.d things...
Mike Meyer wrote: Yes, that's correct. And yes, not all is bad in SysV. In particular, having a directory where you can find scripts to stop (and restart) subsystems is very nice. I think the multiple levels (rc?.d) is a bit of overkill. Either the system is up (meaning everything is turned on), or it's down, and the sysadmin who brought it down can start the subsystems s/he needs. Having a single init.d to look in for those things helps in that process. The multiple levels are there to deal with changes in state. In BSD, for instance, we have single user/multi-user. A number of other variations can exist, both in heavy duty servers where you might want to bring certain services down for upgrade and then back up, and "desktop" machines, such as notebooks where you can be stand-alone, docked into different networks (eg. home/work). Thing is, SysV does it in a very ugly way, and not flexible enough either. This has been talked to death. Look at these: http://www.freebsd.org/~dfr/devices.html http://www.freebsd.org/~eivind/newrc.html and my favorite substitute proposal: http://www.roguetrader.com/~brandon/sas/. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] jkh _DES: The Book of Bruce has only one sentence in it, and it says "the actual directives of my cult are left as an exercise for the reader. Good luck." EE jkh: does it really include the 'good luck' part? jkh EE: OK, I made that part up. jkh EE: I figured it should sound a bit more cheery than how Bruce initially dictated it to me. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sudden CURRENT-crashes
As of a buildworld/installworld several hours ago CURRENT is constantly crashing from underneath me: [ output from uname -a ]-- FreeBSD shadowmere.student.utwente.nl 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Mon Jul 10 14:33:42 CEST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/ARSENIC i386 I managed to get one crash-dump (i don't know how to actually debug this but if someone can give me directions i would like to help out) i have attached dmesg output, as well as a kgdb-session taken as far as i could from from the example in the Handbook ... This has just started happening with this specific CURRENT. -- Pascal Hofstee daeron @ shadowmere . student . utwente . nl Managers know it must be good because the programmers hate it so much. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Mon Jul 10 14:33:42 CEST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/ARSENIC Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 336803605 Hz CPU: AMD-K6(tm) 3D processor (336.80-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX AMD Features=0x8800SYSCALL,3DNow! real memory = 100663296 (98304K bytes) avail memory = 95244288 (93012K bytes) Preloaded elf kernel "kernel" at 0xc029b000. Preloaded elf module "randomdev.ko" at 0xc029b09c. K6-family MTRR support enabled (2 registers) npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 pci0: Intel 82439TX System controller (MTXC) at 0.0 isab0: Intel 82371AB PCI to ISA bridge at device 1.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xe000-0xe00f at device 1.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: Intel 82371AB/EB (PIIX4) USB controller at 1.2 intpm0: Intel 82371AB Power management controller port 0xe800-0xe80f irq 9 at device 1.3 on pci0 intpm0: I/O mapped e800 intpm0: intr IRQ 9 enabled revision 0 smbus0: System Management Bus on intsmb0 smb0: SMBus general purpose I/O on smbus0 intpm0: PM I/O mapped e400 pci0: S3 ViRGE DX/GX graphics accelerator at 10.0 irq 9 pci0: unknown card (vendor=0x10d9, dev=0x0512) at 11.0 irq 11 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse flags 0x4 irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 ed0 at port 0x300-0x31f iomem 0xd8000-0xdbfff irq 10 on isa0 ed0: address 00:00:c0:f0:38:c4, type SMC8216/SMC8216C (16 bit) fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 isa0: @@@ found sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 isa0: @@@ found isa0: @@@ found isa0: PNP0400 found unknown: PNP0501 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0700 can't assign resources unknown: PNP0f13 can't assign resources unknown: PNP0303 can't assign resources isa0: PNP0800 found unknown: PNP0c02 can't assign resources IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to deny, unlimited logging ata0-master: DMA limitted to UDMA33, non-ATA66 compliant cable ad0: 17624MB QUANTUM FIREBALLP KA18.2 [35808/16/63] at ata0-master using UDMA33 ad1: 9671MB IBM-DTTA-351010 [19650/16/63] at ata1-master using UDMA33 acd0: CD-RW R/RW 4x4x24 at ata0-slave using WDMA2 Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted dc0: Macronix 98713 10/100BaseTX port 0xd400-0xd4ff mem 0xdf80-0xdf8000ff irq 11 at device 11.0 on pci0 dc0: Ethernet address: 00:00:b4:74:58:43 miibus0: MII bus on dc0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Script started on Mon Jul 10 17:41:21 2000 101 shadowmere ~ # cd /usr/src/sys/compile/ARSENIC/ 102 shadowmere ARSENIC # gdb -k kernel.debug /var/crash/vmcore.3 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 2805760 initial pcb at 2347e0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x771d538 fault code = supervisor read,
Perl 5.6.0 pod2man ports
Hi,
after the messages about the perl update have settled I decided to
update my perl-ports (p5-*), but I get a warning (the "echo $(PATH)"
below is inserted into the port Makefile by me).
---snip---
{0} [Magelan:/usr/ports/lang/p5-F77]
(28) root@ttyp1# make configure
=== Extracting for p5-ExtUtils-F77-1.12
Checksum OK for ExtUtils-F77-1.12.tar.gz.
=== Patching for p5-ExtUtils-F77-1.12
=== Configuring for p5-ExtUtils-F77-1.12
echo
/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin:/usr/X11R6/bin:/usr/games:/root/bin
/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin:/usr/X11R6/bin:/usr/games:/root/bin
Checking if your kit is complete...
Looks good
Warning: I could not locate your pod2man program. Please make sure,
your pod2man program is in your PATH before you execute 'make'
Writing Makefile for ExtUtils::F77
{0} [Magelan:/usr/ports/lang/p5-F77]
(29) root@ttyp1# ll /usr/bin/pod2man
-r-xr-xr-x 1 root wheel 16613 Jul 8 22:03 /usr/bin/pod2man*
---snip---
This applys to many p5 ports.
The world is from Jul 8 (what about adding the output of 'date' into the
output of (build|install)world by default?), ports are from today
(around 2pm).
Is this something unresolved or is this related to my system only (is
someone able to reproduce this)?
Bye,
Alexander.
--
Weird enough for government work.
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Perl 5.6.0 pod2man ports
On Mon, Jul 10, 2000 at 06:32:22PM +0200, Sheldon Hearn wrote:
But you didn't update /usr/ports/Mk, did you? :-)
This is nothing to do with parts of /usr/ports being out of date
and has already been mentioned on both -ports and -current.
From my -current box, which is most definitely up to date
(both src/ and ports/ from 7/9):
[choose random p5 port]
coredump 278# make
=== Extracting for p5-Convert-UU-0.40
expr in free(): warning: modified (chunk-) pointer.
Checksum OK for Convert-UU-0.40.tar.gz.
=== Patching for p5-Convert-UU-0.40
=== Configuring for p5-Convert-UU-0.40
Checking if your kit is complete...
Looks good
Warning: I could not locate your pod2man program. Please make sure,
your pod2man program is in your PATH before you execute 'make'
Writing Makefile for Convert::UU
=== Building for p5-Convert-UU-0.40
[...]
The following (untested, by me) patch from
MANTANI Nobutaka [EMAIL PROTECTED] apparently fixes this.
--- /usr/src/contrib/perl5/lib/ExtUtils/MM_Unix.pm.orig Tue Jul 4 10:33:51 2000
+++ /usr/src/contrib/perl5/lib/ExtUtils/MM_Unix.pm Tue Jul 4 10:34:33 2000
@@ -1353,7 +1353,7 @@
if (defined $self-{PERL_SRC}) {
$pod2html_exe = $self-catfile($self-{PERL_SRC},'pod','pod2html');
} else {
- $pod2html_exe = $self-catfile($Config{scriptdirexp},'pod2html');
+ $pod2html_exe = $self-catfile($Config{bin},'pod2html');
}
unless ($pod2html_exe = $self-perl_script($pod2html_exe)) {
# No pod2html but some HTMLxxxPODS to be installed
@@ -2608,7 +2608,7 @@
if (defined $self-{PERL_SRC}) {
$pod2man_exe = $self-catfile($self-{PERL_SRC},'pod','pod2man');
} else {
- $pod2man_exe = $self-catfile($Config{scriptdirexp},'pod2man');
+ $pod2man_exe = $self-catfile($Config{bin},'pod2man');
}
unless ($pod2man_exe = $self-perl_script($pod2man_exe)) {
# Maybe a build by uninstalled Perl?
-aDe
--
Ade Lovett, Austin, TX. [EMAIL PROTECTED]
FreeBSD: The Power to Serve http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Perl 5.6.0 pod2man ports
On Mon, Jul 10, 2000 at 06:32:22PM +0200, Sheldon Hearn wrote: But you didn't update /usr/ports/Mk, did you? :-) This is nothing to do with parts of /usr/ports being out of date and has already been mentioned on both -ports and -current. Will fix now... M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
New version of TAP driver for FreeBSD -current
Hello All, The new version of TAP driver for FreeBSD -current is available at http://home.earthlink.net/~evmax/tap-fbsd5.tar.gz Changes: - small bug fixes, code improvements and cleanup - man page (derived from tun(4)) - if_tap module can be unloaded now (works for me, but please test it) - standalone Makefile (to build module outside of main source tree) Long time back i sent request to the list and asked about including this driver into the source tree. i still did not receive any reply. Some people seems to be using this driver for Ethernet tunneling (with VTUN software). Somebody even requested for OpenBSD port. So it would be really nice to hear from one of the commiters. Thanks, emax To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl 5.6.0 pod2man ports
On 10 Jul, Ade Lovett wrote: But you didn't update /usr/ports/Mk, did you? :-) Only if ports-base isn't anymore in ports-all or my local CVS tree is messed up. But you didn't do an »grep -i pod /usr/ports/Mk/*«, did you? :-) This is nothing to do with parts of /usr/ports being out of date and has already been mentioned on both -ports and -current. It was really mentioned on -current? Do you have a MessageID at hand (I haven't seen such a message, it would lead to the conclusion that my mailsystem is faulty (invariant: I haven't overlooked the message))? The following (untested, by me) patch from MANTANI Nobutaka [EMAIL PROTECTED] apparently fixes this. I give it a try. Thanks, Alexander. -- Intel: where Quality is job number 0.9998782345! http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: etc/rc.d things...
Johan, I quite agree that in the simple but better approach of rc.conf (BSD). However I like the idea of a configurable, directory driven approach to the shutdown. I would be apposed to sysV style rc.d's as I really don't think they provide anything but confusion. At the ISP where I work the BSD model is far easier to maintain. Personally far easier than the solaris, hp-ux, and linux machines we've had in the past Johan Granlund wrote: Please Please Please _Dont_!!! I dont know if someone is yoking, my english is not up to that :( I tried to secure a Solaris machine and hated the whole setup. I't have some good things but i take the simple rc.conf mechanism every time! /Johan On Mon, 10 Jul 2000, Mikel wrote: Kelly Yancey wrote: On Sat, 8 Jul 2000, Mike Meyer wrote: By all means, use start/stop args, but hard link the .sh files into seperate directories or something so that the order can be tweaked.. If all you want is to make sure that shutdown happens in the reverse order of startup, that can be done by reversing the list in rc.shutdown. But how about going a step further, and starting towards a user-friendly configuration process? Instead of being globbed at init time, etc/rc.d is a repository for things that take start/stop arguments. They are symlinked to /etc/init.d with numeric prefixes to control order at initialization time. Likewise, they can be symlinked to /etc/down.d (or shutdown.d) with numeric prefixes to control order at shutdown time. How about rather then separate directories, you prefix the symlink names with 'S' for startup scripts and 'K' (for "kill") for shutdown scripts. Then, you rename rc.d to rc3.d... I like it. It's clean and simple, almost to the point of being elegant. But why bother adding rc?.d if you are going to right it to handle s or k then the present home should be fine, no? Ducks and runs, Kelly -- Kelly Yancey - [EMAIL PROTECTED] - Belmont, CA System Administrator, eGroups.com http://www.egroups.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Cheers, Mikel +~+ | Optimized Computer Solutions, Inchttp://www.ocsny.com | 39 W14th Street, Suite 203 212 727 2238 x132 | New York, NY 10011 +~+ -- Cheers, Mikel +~+ | Optimized Computer Solutions, Inchttp://www.ocsny.com | 39 W14th Street, Suite 203 212 727 2238 x132 | New York, NY 10011 +~+ begin:vcard n:King;Mikel tel;fax:2124638402 tel;home:http://www.upan.org tel;work:2127272100 x-mozilla-html:TRUE org:Optimized Computer Solutions version:2.1 email;internet:[EMAIL PROTECTED] title:Director of Network Operations Technology adr;quoted-printable:;;39 W14th St.=0D=0ASte 203;New York;NY;10011;US note;quoted-printable:fBSD, PHP, MySql and OCS Rule!!!=0D=0A=0D=0AGoal is to be MS free by the end of 2k. x-mozilla-cpt:;7312 fn:Mikel King end:vcard
Current Spontaneous Reboot
I just experienced a sudden reboot. I am running -current SMP. Cvsup, make world, rebuild kernel 2709. # uname -a FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #0: \ Sun Jul 9 18:05:19 PDT 2000 \ root@celebris:/usr/src/sys/compile/CELEBRIS-SMP i386 The system was very lightly loaded. I was running emacs creating a shell script. When the reboot happened, I was attempting to go up the tcsh history chain. I pressed the up arrow several times and the system froze for a few seconds and rebooted. It did not drop into the debugger. I have options DDB options KTRACE #kernel tracing in the config. After the 'world and new kernel on 2709, I did a 'make world' on 2710, testing stability. No problems, although the time increased by an hour to 9 hours. tomdean = config # # CELEBRIS-SMP # machine i386 cpu I586_CPU ident CELEBRIS hints "CELEBRIS.hints" maxusers50 ## # # options from mptable # #MPTable, version 2.0.11 # #-- # #MP Floating Pointer Structure: # # #location: EBDA # physical address: 0x0009fc30 # signature:'_MP_' # length: 16 bytes # version: 1.1 # checksum: 0x55 # mode: Virtual Wire # #-- # # MP default config type: 5 # # bus: ISA+PCI, APIC: Integrated # #-- # # SMP kernel config file options: # Required: options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Lets always enable the kernel debugger for SMP. options DDB #makeoptionsDEBUG=-g ## options INET#InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660"#ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=1#Be pessimistic about Joe SCSI device options UCONSOLE#Allow users to grab the console options MSGBUF_SIZE=(10*PAGE_SIZE) #System Message Buffer Size options SYSVSHM # for X11 options SYSVSEM # for X11 options SYSVMSG # for X11 options RANDOMDEV #entropy device #optionsPSM_CHECKSYNC # resync when switch console modes #config kernel root on da1 device isa device pci options COMPAT_OLDPCI #Use PCI shims and glue for old drivers device fdc # # FDC_DEBUG enables floppy debugging. Since the debug output is huge, you # gotta turn it actually on by setting the variable fd_debug with DDB, # however. options FDC_DEBUG #tape ft0 at fdc0 drive 2 device ncr device scbus device da # SCSI Direct Access Device device sa # SCSI Tape device cd #Only need one of these, the code dynamically grows # The keyboard device; it controlls the keyboard and the PS/2 mouse. device atkbdc # The AT keyboard device atkbd # `flags' for atkbd: # 0x01Force detection of keyboard, else we always assume a keyboard # 0x02Don't reset keyboard, useful for some newer ThinkPads # 0x04Old-style (XT) keyboard support, useful for older ThinkPads device psm # The video card driver. device vga # Splash screen at start up! Screen savers require this too. device splash # syscons is the default console driver, resembling an SCO console device sc device npx device sio device sio # Parallel-Port Bus # nlpt Parallel Printer device ppbus device lpt device ppc device de # DEC DC21040 Ethernet Adapter device loop device ether device tun 1 device bpf4 #Berkeley packet filter device vn #Vnode driver (turns a file into a device) device snp 3 #Snoop device - to look at pty/vty/etc.. device pty 16 device gzip# Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options
Re: etc/rc.d things...
Andrzej Bialecki wrote: and my favorite substitute proposal: http://www.roguetrader.com/~brandon/sas/. I really like the ideas in the last one. The pages were not updated for some time - do you know if the author still works on it? No clue. At the time he decided to have a take on it, I traded many messages with him about it. I know he had part of it working, and could boot with it. After that, though, I never heard from him again. Like you, I really like his proposal. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] jkh _DES: The Book of Bruce has only one sentence in it, and it says "the actual directives of my cult are left as an exercise for the reader. Good luck." EE jkh: does it really include the 'good luck' part? jkh EE: OK, I made that part up. jkh EE: I figured it should sound a bit more cheery than how Bruce initially dictated it to me. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl 5.6.0 pod2man ports
On Mon, 10 Jul 2000 11:44:08 EST, Ade Lovett wrote: On Mon, Jul 10, 2000 at 06:32:22PM +0200, Sheldon Hearn wrote: But you didn't update /usr/ports/Mk, did you? :-) This is nothing to do with parts of /usr/ports being out of date and has already been mentioned on both -ports and -current. Interesting. I was seeing these exact error messages until I updated /usr/ports/Mk, after which they went away. Sorry to have misinformed. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: etc/rc.d things...
On Tue, 11 Jul 2000, Daniel C. Sobral wrote: Andrzej Bialecki wrote: and my favorite substitute proposal: http://www.roguetrader.com/~brandon/sas/. I really like the ideas in the last one. The pages were not updated for some time - do you know if the author still works on it? No clue. At the time he decided to have a take on it, I traded many messages with him about it. I know he had part of it working, and could boot with it. After that, though, I never heard from him again. Like you, I really like his proposal. Hmm... Soon I will have some free time (holidays and stuff..). I'll take a look at it. It looks too good to be wasted. Andrzej Bialecki // [EMAIL PROTECTED] WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
if_de as a module...
Hi Bill If I apply the enclosed patch to sys/pci/if_de.c, and make a copy of (say) sys/modules/dc to sys/modules/de (while changing all relevant dc -- de), I can build a loadable module for de. Could you please check that this works in your (no doubt) excellent laboratory and either commit or review for me to commit. Thanks! :-) M Index: sys/pci/if_de.c === RCS file: /home/ncvs/src/sys/pci/if_de.c,v retrieving revision 1.129 diff -u -d -r1.129 if_de.c --- sys/pci/if_de.c2000/05/28 16:06:56 1.129 +++ sys/pci/if_de.c 2000/07/09 08:27:09 @@ -54,10 +54,9 @@ #include sys/bus.h #include sys/rman.h -#include "opt_inet.h" -#include "opt_ipx.h" - #include net/if.h +#include net/if_arp.h +#include net/ethernet.h #include net/if_media.h #include net/if_dl.h #ifdef TULIP_USE_SOFTINTR To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: if_de as a module...
*I'll* check it too- I'd *love* to have if_de as a loadable since most of the alphas I have use if_de (not dc)! On Mon, 10 Jul 2000, Mark Murray wrote: Hi Bill If I apply the enclosed patch to sys/pci/if_de.c, and make a copy of (say) sys/modules/dc to sys/modules/de (while changing all relevant dc -- de), I can build a loadable module for de. Could you please check that this works in your (no doubt) excellent laboratory and either commit or review for me to commit. Thanks! :-) M Index: sys/pci/if_de.c === RCS file: /home/ncvs/src/sys/pci/if_de.c,v retrieving revision 1.129 diff -u -d -r1.129 if_de.c --- sys/pci/if_de.c 2000/05/28 16:06:56 1.129 +++ sys/pci/if_de.c 2000/07/09 08:27:09 @@ -54,10 +54,9 @@ #include sys/bus.h #include sys/rman.h -#include "opt_inet.h" -#include "opt_ipx.h" - #include net/if.h +#include net/if_arp.h +#include net/ethernet.h #include net/if_media.h #include net/if_dl.h #ifdef TULIP_USE_SOFTINTR To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: etc/rc.d things...
"Daniel C. Sobral" [EMAIL PROTECTED] writes: Mike Meyer wrote: Yes, that's correct. And yes, not all is bad in SysV. In particular, having a directory where you can find scripts to stop (and restart) subsystems is very nice. I think the multiple levels (rc?.d) is a bit of overkill. Either the system is up (meaning everything is turned on), or it's down, and the sysadmin who brought it down can start the subsystems s/he needs. Having a single init.d to look in for those things helps in that process. The multiple levels are there to deal with changes in state. In BSD, for instance, we have single user/multi-user. A number of other variations can exist, both in heavy duty servers where you might want to bring certain services down for upgrade and then back up, and "desktop" machines, such as notebooks where you can be stand-alone, docked into different networks (eg. home/work). Thing is, SysV does it in a very ugly way, and not flexible enough either. This has been talked to death. Look at these: http://www.freebsd.org/~dfr/devices.html off topic. http://www.freebsd.org/~eivind/newrc.html well. what about a mix of the SystemV approach (ala HP-UX) and the IRIX one (using something like chconfig). HP-UX : /sbin/init.d/script start_msg|stop_msg|start|stop (FMPOV, there isn't not enough possible choises, such as status, restart, config, command, etc.) /sbin/rc[S0-5].d/[SK][0-9][0-9][0-9]script linked to /sbin/init.d/script /sbin/rc (+ /sbin/rc.util) sources /etc/rc.config then runs /sbin/rc?.d startup files /etc/rc.config.d/services are configuration files (ala bourne shell). /sbin/rc.config sources /etc/rc.config.d configuration files. /usr/sbin/ch_rc is not so easy to use to modify /etc/rc.config.d/services. IRIX : oops, don't remember how works startup scripts. I just remember me configurations files : /sbin/chconfig [on|off] service or something like that. (don't remember if it's possible to change options through chconfig, but I guess no). /etc/config/services enable or disable services. /etc/config/services.options just contains arguments to services. so, a mix of both w/o the levels stuffs + a /etc/rc.default.d (a synonym to /etc/defaults/rc.conf but in separate files between HP-UX and IRIX configuration files) would be a begining. please, don't do something like AIX :) they use a binary database to stock there things... and my favorite substitute proposal: http://www.roguetrader.com/~brandon/sas/. effectively, the last one is interresting. a major problem w/ this one is the use of "perl" which is not available a boot time since it is located in /usr. Cyrille. -- home:mailto:[EMAIL PROTECTED] Supprimer "%no-spam" pour me repondre. work:mailto:[EMAIL PROTECTED] Remove "%no-spam" to answer me back. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: if_de as a module...
*I'll* check it too- I'd *love* to have if_de as a loadable since most of the alphas I have use if_de (not dc)! Umm- started okay: de0: Digital 21140A Fast Ethernet port 0x10300-0x1037f mem 0x82083000-0x8208307f irq 3 at device 9.0 on pci0 de0: interrupting at CIA irq 3 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:40:05:41:5b:e6 bpf: de0 attached de0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.67.166.23 netmask 0xff00 broadcast 192.67.166.255 ether 00:40:05:41:5b:e6 media: autoselect supported media: autoselect 100baseTX full-duplex 100baseTX 10baseT/UTP full-duplex 10baseT/UTP lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 add net default: gateway 192.67.166.1 Additional routing options: tcp arplookup 192.67.166.155 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 192.67.166.155rt extensions=NO IP gateway=YES TCP keepalive=YES. routing daemons:. ... but then failed with: arplookup 192.67.166.155 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 192.67.166.155rt arplookup 192.67.166.155 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 192.67.166.155rt arplookup 192.67.166.155 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 192.67.166.155rt and then died: rplookup 192.67.166.155 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 192.67.166.155rt arplookup 192.67.166.155 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 192.67.166.155rt arplookup 192.67.166.155 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 192.67.166.155rt NFS Portmap: RPC: Port mapper failure - RPC: Timed out fatal kernel trap: trap entry = 0x2 (memory management fault) a0 = 0x0 a1 = 0x1 a2 = 0x pc = 0x0 ra = 0xfc4cb4e0 curproc= 0 ddbprinttrap from 0x0 ddbprinttrap(0x0, 0x1, 0x, 0x2) panic: trap panic Stopped at Debugger+0x2c: ldq ra,0(sp) 0xfe0009805a00 ra=0xfc4d0ca0,sp=0xfe0009805a00 db t Debugger() at Debugger+0x2c panic() at panic+0x100 trap() at trap+0x630 XentMM() at XentMM+0x20 swi_net() at swi_net+0x40 (null)() at 0x1 --- *sigh* (whimper) On Mon, 10 Jul 2000, Mark Murray wrote: Hi Bill If I apply the enclosed patch to sys/pci/if_de.c, and make a copy of (say) sys/modules/dc to sys/modules/de (while changing all relevant dc -- de), I can build a loadable module for de. Could you please check that this works in your (no doubt) excellent laboratory and either commit or review for me to commit. Thanks! :-) M Index: sys/pci/if_de.c === RCS file: /home/ncvs/src/sys/pci/if_de.c,v retrieving revision 1.129 diff -u -d -r1.129 if_de.c --- sys/pci/if_de.c2000/05/28 16:06:56 1.129 +++ sys/pci/if_de.c 2000/07/09 08:27:09 @@ -54,10 +54,9 @@ #include sys/bus.h #include sys/rman.h -#include "opt_inet.h" -#include "opt_ipx.h" - #include net/if.h +#include net/if_arp.h +#include net/ethernet.h #include net/if_media.h #include net/if_dl.h #ifdef TULIP_USE_SOFTINTR To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: if_de as a module...
Umm- started okay: : and then died: rplookup 192.67.166.155 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 192.67.166.155rt arplookup 192.67.166.155 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 192.67.166.155rt arplookup 192.67.166.155 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 192.67.166.155rt NFS Portmap: RPC: Port mapper failure - RPC: Timed out Bleagh. Fooey. :-( Biiilll!!?? :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
freeing free cluster?
-current, as of ~today: FreeBSD/alpha (farrago.feral.com) (console) login: panic: freeing free cluster panic Stopped at Debugger+0x2c: ldq ra,0(sp) 0xfe000a2019f0 ra=0xfc4dbd40,sp=0xfe000a2019f0 db t Debugger() at Debugger+0x2c panic() at panic+0x100 m_freem() at m_freem+0x134 nfs_writerpc() at nfs_writerpc+0x1130 nfs_doio() at nfs_doio+0x614 nfssvc_iod() at nfssvc_iod+0x264 nfssvc() at nfssvc+0xa8 syscall() at syscall+0x244 XentSys() at XentSys+0x50 (null)() at 0x12680 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: etc/rc.d things...
On 10 Jul 2000, Cyrille Lefevre wrote: and my favorite substitute proposal: http://www.roguetrader.com/~brandon/sas/. effectively, the last one is interresting. a major problem w/ this one is the use of "perl" which is not available a boot time since it is located in /usr. If we find out that it's very interesting, it should be implemented as part of init(8). (hint: init is NOT Perl based ;-) Andrzej Bialecki // [EMAIL PROTECTED] WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: if_de as a module...
The opt_ files can be generated by the makefiles, so there is no reason to remove those, see sys/modules/usb/Makefile SRCS = bus_if.h device_if.h usb_if.h usb_if.c \ vnode_if.h \ opt_usb.h \ ... Any file called opt_*.h that is not present is created (empty). Nick *I'll* check it too- I'd *love* to have if_de as a loadable since most of the alphas I have use if_de (not dc)! On Mon, 10 Jul 2000, Mark Murray wrote: Hi Bill If I apply the enclosed patch to sys/pci/if_de.c, and make a copy of (say) sys/modules/dc to sys/modules/de (while changing all relevant dc -- de), I can build a loadable module for de. Could you please check that this works in your (no doubt) excellent laboratory and either commit or review for me to commit. Thanks! :-) M Index: sys/pci/if_de.c === RCS file: /home/ncvs/src/sys/pci/if_de.c,v retrieving revision 1.129 diff -u -d -r1.129 if_de.c --- sys/pci/if_de.c2000/05/28 16:06:56 1.129 +++ sys/pci/if_de.c 2000/07/09 08:27:09 @@ -54,10 +54,9 @@ #include sys/bus.h #include sys/rman.h -#include "opt_inet.h" -#include "opt_ipx.h" - #include net/if.h +#include net/if_arp.h +#include net/ethernet.h #include net/if_media.h #include net/if_dl.h #ifdef TULIP_USE_SOFTINTR To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: if_de as a module...
Umm- started okay: : and then died: rplookup 192.67.166.155 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 192.67.166.155rt arplookup 192.67.166.155 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 192.67.166.155rt arplookup 192.67.166.155 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 192.67.166.155rt NFS Portmap: RPC: Port mapper failure - RPC: Timed out Bleagh. Fooey. :-( Biiilll!!?? :-) I don't think this is Bill. What does the output of netstat -rn | grep 192.67.166.155 look like when the above is occuring? I am having similiar problems here, I just upgraded one of our main boarder routers and started getting this stuff. Is what is happening is a host specific route is getting installed by gated, and this is causing arplookup/arpresolve to have problems when it tries to go create the llinfo. We just upgraded this router from 3.4-stable of January vintage to 4.0-STABLE FreeBSD July 2 vintage. I have seen this in the past, and though it was long gone, but now that I am looking at it again I see what is happening, The message we get is the same as yours: Jul 9 17:37:02 br1 /kernel: arplookup 205.238.40.30 failed: could not allocate llinfo Jul 9 17:37:02 br1 /kernel: arpresolve: can't allocate llinfo for 205.238.40.30 rt Now if I look in my routing table when this is going on (sorry don't have it saved off anyplace I can cut and paste from right now) I see a host route out another interface!!! Yes, we have a large ospf network, yes that route will work, no it is not the right route damn it, there is a direct route via an interface, and we are trying to use it, but something is blowing chunks in rtalloc1. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: freeing free cluster?
On Mon, Jul 10, 2000 at 01:15:20PM -0700, Matthew Jacob wrote: -current, as of ~today: FreeBSD/alpha (farrago.feral.com) (console) login: panic: freeing free cluster panic Stopped at Debugger+0x2c: ldq ra,0(sp) 0xfe000a2019f0 ra=0xfc4dbd40,sp=0xfe000a2019f0 I am getting a very strong suspicion, this is the same bug i have reported earlier as well as DES did in another message. Anyone here that is able to shed some more light on it ? -- Pascal Hofstee daeron @ shadowmere . student . utwente . nl Managers know it must be good because the programmers hate it so much. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: freeing free cluster?
Nope, not for me. I probably have a core dump, but because gdb is busted for alpha in -current, it won't say much. On Mon, 10 Jul 2000, Pascal Hofstee wrote: On Mon, Jul 10, 2000 at 01:15:20PM -0700, Matthew Jacob wrote: -current, as of ~today: FreeBSD/alpha (farrago.feral.com) (console) login: panic: freeing free cluster panic Stopped at Debugger+0x2c: ldq ra,0(sp) 0xfe000a2019f0 ra=0xfc4dbd40,sp=0xfe000a2019f0 I am getting a very strong suspicion, this is the same bug i have reported earlier as well as DES did in another message. Anyone here that is able to shed some more light on it ? -- Pascal Hofstee daeron @ shadowmere . student . utwente . nl Managers know it must be good because the programmers hate it so much. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: if_de as a module...
This doesn't happen for me except in this (loadable de) case. On Mon, 10 Jul 2000, Rodney W. Grimes wrote: Umm- started okay: : and then died: rplookup 192.67.166.155 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 192.67.166.155rt arplookup 192.67.166.155 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 192.67.166.155rt arplookup 192.67.166.155 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 192.67.166.155rt NFS Portmap: RPC: Port mapper failure - RPC: Timed out Bleagh. Fooey. :-( Biiilll!!?? :-) I don't think this is Bill. What does the output of netstat -rn | grep 192.67.166.155 look like when the above is occuring? I am having similiar problems here, I just upgraded one of our main boarder routers and started getting this stuff. Is what is happening is a host specific route is getting installed by gated, and this is causing arplookup/arpresolve to have problems when it tries to go create the llinfo. We just upgraded this router from 3.4-stable of January vintage to 4.0-STABLE FreeBSD July 2 vintage. I have seen this in the past, and though it was long gone, but now that I am looking at it again I see what is happening, The message we get is the same as yours: Jul 9 17:37:02 br1 /kernel: arplookup 205.238.40.30 failed: could not allocate llinfo Jul 9 17:37:02 br1 /kernel: arpresolve: can't allocate llinfo for 205.238.40.30 rt Now if I look in my routing table when this is going on (sorry don't have it saved off anyplace I can cut and paste from right now) I see a host route out another interface!!! Yes, we have a large ospf network, yes that route will work, no it is not the right route damn it, there is a direct route via an interface, and we are trying to use it, but something is blowing chunks in rtalloc1. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: if_de as a module...
This doesn't happen for me except in this (loadable de) case. Well a bit more digging... netstat -rn 205.238.40.30 205.238.40.30 UHW18 2563 dc0860 Now why oh why is gated and/or the kernel creating that route when ifconfig dc0 dc0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 205.238.40.1 netmask 0xffe0 broadcast 205.238.40.31 ether 00:80:c8:57:cc:45 media: autoselect (10baseT/UTP) status: active supported media: autoselect 100baseTX full-duplex 100baseTX 10baseT/UTP full-duplex 10baseT/UTP none Now, 205.238.40.30 is a router, this route is visible in ospf, here on the originating box: 205.238.40.30/32 - local CP 0 0 11049 11702 and here on another gated/FreeBSD box: 205.238.40.30 198.145.92.1 UGH 1 932 de1 and here from a Cisco: O 205.238.40.30/32 [110/440] via 205.238.44.1, 00:07:33, Ethernet0 Now, what in the hell is deleting the normal arp: ? (205.238.40.30) at 0:c0:7b:6a:28:f0 [ethernet] and replacing it with the above 205.238.40.30/205.238.40.30 route. I've even done an ``arp -S 205.238.40.30 0:c0:7b:6a:28:f0'' to create a ``permanant'' entry and IT gets replaced!!! ARGHHH On Mon, 10 Jul 2000, Rodney W. Grimes wrote: Umm- started okay: : and then died: rplookup 192.67.166.155 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 192.67.166.155rt arplookup 192.67.166.155 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 192.67.166.155rt arplookup 192.67.166.155 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 192.67.166.155rt NFS Portmap: RPC: Port mapper failure - RPC: Timed out Bleagh. Fooey. :-( Biiilll!!?? :-) I don't think this is Bill. What does the output of netstat -rn | grep 192.67.166.155 look like when the above is occuring? I am having similiar problems here, I just upgraded one of our main boarder routers and started getting this stuff. Is what is happening is a host specific route is getting installed by gated, and this is causing arplookup/arpresolve to have problems when it tries to go create the llinfo. We just upgraded this router from 3.4-stable of January vintage to 4.0-STABLE FreeBSD July 2 vintage. I have seen this in the past, and though it was long gone, but now that I am looking at it again I see what is happening, The message we get is the same as yours: Jul 9 17:37:02 br1 /kernel: arplookup 205.238.40.30 failed: could not allocate llinfo Jul 9 17:37:02 br1 /kernel: arpresolve: can't allocate llinfo for 205.238.40.30 rt Now if I look in my routing table when this is going on (sorry don't have it saved off anyplace I can cut and paste from right now) I see a host route out another interface!!! Yes, we have a large ospf network, yes that route will work, no it is not the right route damn it, there is a direct route via an interface, and we are trying to use it, but something is blowing chunks in rtalloc1. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current Spontaneous Reboot
Just a "me too" While telnetting to another machine, I suddenly got a "Page not present in supervisor mode", and a reference to rc5des. Unfortunately I hit the "any-key" too fast to provide any more info. Leif - Original Message - From: "Thomas D. Dean" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, July 10, 2000 8:01 PM Subject: Current Spontaneous Reboot I just experienced a sudden reboot. I am running -current SMP. Cvsup, make world, rebuild kernel 2709. # uname -a FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #0: \ Sun Jul 9 18:05:19 PDT 2000 \ root@celebris:/usr/src/sys/compile/CELEBRIS-SMP i386 The system was very lightly loaded. I was running emacs creating a shell script. When the reboot happened, I was attempting to go up the tcsh history chain. I pressed the up arrow several times and the system froze for a few seconds and rebooted. It did not drop into the debugger. I have options DDB options KTRACE #kernel tracing in the config. After the 'world and new kernel on 20000709, I did a 'make world' on 2710, testing stability. No problems, although the time increased by an hour to 9 hours. tomdean = config # # CELEBRIS-SMP # machine i386 cpu I586_CPU ident CELEBRIS hints "CELEBRIS.hints" maxusers 50 ## # # options from mptable # #MPTable, version 2.0.11 # #-- # #MP Floating Pointer Structure: # # #location: EBDA # physical address: 0x0009fc30 # signature:'_MP_' # length: 16 bytes # version: 1.1 # checksum: 0x55 # mode: Virtual Wire # #-- # # MP default config type: 5 # # bus: ISA+PCI, APIC: Integrated # #-- # # SMP kernel config file options: # Required: options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Lets always enable the kernel debugger for SMP. options DDB #makeoptions DEBUG=-g ## options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=1 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options MSGBUF_SIZE=(10*PAGE_SIZE) #System Message Buffer Size options SYSVSHM # for X11 options SYSVSEM # for X11 options SYSVMSG # for X11 options RANDOMDEV #entropy device #options PSM_CHECKSYNC # resync when switch console modes #config kernel root on da1 device isa device pci options COMPAT_OLDPCI #Use PCI shims and glue for old drivers device fdc # # FDC_DEBUG enables floppy debugging. Since the debug output is huge, you # gotta turn it actually on by setting the variable fd_debug with DDB, # however. options FDC_DEBUG #tape ft0 at fdc0 drive 2 device ncr device scbus device da # SCSI Direct Access Device device sa # SCSI Tape device cd #Only need one of these, the code dynamically grows # The keyboard device; it controlls the keyboard and the PS/2 mouse. device atkbdc # The AT keyboard device atkbd # `flags' for atkbd: # 0x01Force detection of keyboard, else we always assume a keyboard # 0x02Don't reset keyboard, useful for some newer ThinkPads # 0x04Old-style (XT) keyboard support, useful for older ThinkPads device psm # The video card driver. device vga # Splash screen at start up! Screen savers require this too. device splash # syscons is the default console driver, resembling an SCO console device sc device npx device sio device sio # Parallel-Port Bus # nlpt Parallel Printer device ppbus device lpt device ppc device de # DEC DC21040 Ethernet Adapter device loop device ether device tun 1 device bpf 4 #Berkeley packet filter device vn #Vnode driver (turns a file into a device) device snp 3 #Snoop device - to look at pty/vty/etc.. device pty 16 device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing = dmesg ===
Re: New version of TAP driver for FreeBSD -current
On Mon, 10 Jul 2000, Yevmenkin, Maksim N, CSCIO wrote: Long time back i sent request to the list and asked about including this driver into the source tree. i still did not receive any reply. Some people seems to be using this driver for Ethernet tunneling (with VTUN software). Somebody even requested for OpenBSD port. So it would be really nice to hear from one of the commiters. You might want to post request for review to the net@ list. If inclusion of if_tap driver will be considered as reasonable I can bring it in the tree. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current Spontaneous Reboot
Me too. But not SMP. - dmesg kernel trap 9 with interrupts disabled Fatal trap 9: general protection fault while in kernel mode instruction pointer = 0x8:0xc030ada4 stack pointer = 0x10:0xcb6b1c30 frame pointer = 0x10:0xcb6b1c80 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 3 current process = 298 (XF86_SVGA.xtt) interrupt mask = trap number = 9 panic: general protection fault syncing disks... 78 Fatal double fault: eip = 0xc02d8bfd esp = 0xcb6afffc ebp = 0xcb6b0090 panic: double fault Uptime: 1h20m34s To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: etc/rc.d things...
Andrzej Bialecki [EMAIL PROTECTED] writes: On 10 Jul 2000, Cyrille Lefevre wrote: and my favorite substitute proposal: http://www.roguetrader.com/~brandon/sas/. effectively, the last one is interresting. a major problem w/ this one is the use of "perl" which is not available a boot time since it is located in /usr. If we find out that it's very interesting, it should be implemented as part of init(8). (hint: init is NOT Perl based ;-) sould be a too big job for init ? mush better to be an external program a la /etc/rc, no ? Cyrille. -- home:mailto:[EMAIL PROTECTED] Supprimer "%no-spam" pour me repondre. work:mailto:[EMAIL PROTECTED] Remove "%no-spam" to answer me back. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: freeing free cluster?
I'm trying to update and isolate the external object reference stuff and am getting page faults in nfs_writebp. Very odd, could be freeing free cluster problem, will perform explicit check and post details. Rebuilding regular non-modified kernel to see if I stumble upon it. On Mon, 10 Jul 2000, Pascal Hofstee wrote: On Mon, Jul 10, 2000 at 01:15:20PM -0700, Matthew Jacob wrote: -current, as of ~today: FreeBSD/alpha (farrago.feral.com) (console) login: panic: freeing free cluster panic Stopped at Debugger+0x2c: ldq ra,0(sp) 0xfe000a2019f0 ra=0xfc4dbd40,sp=0xfe000a2019f0 I am getting a very strong suspicion, this is the same bug i have reported earlier as well as DES did in another message. Anyone here that is able to shed some more light on it ? -- Pascal Hofstee daeron @ shadowmere . student . utwente . nl Managers know it must be good because the programmers hate it so much. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Bosko Milekic * Voice/Mobile: 514.865.7738 * Pager: 514.921.0237 [EMAIL PROTECTED] * http://www.technokratis.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: etc/rc.d things...
Daniel C. Sobral writes: Mike Meyer wrote: The multiple levels are there to deal with changes in state. In BSD, for instance, we have single user/multi-user. A number of other variations can exist, both in heavy duty servers where you might want to bring certain services down for upgrade and then back up, and "desktop" machines, such as notebooks where you can be stand-alone, docked into different networks (eg. home/work). I'm familiar with why mutliple levels exist. I've never run into a system that had a real use for more than three run levels - powered off, maintenance, and up - though I've not dealt with notebooks. Needing to shut down some services in the up mode, or start some in the maintenance mode, is why having "start" and "stop" arguments to the scripts in rc.d is nice. If you find yourself needing to change to the state on a fixed bag of servers regularly, that feature on the scripts allows any admin worth hiring to write scripts to go back and forth easier than they can configure the SysV run levels. This doesn't work very well for the notebook example, though. Thing is, SysV does it in a very ugly way, and not flexible enough either. The functionality SysV provides isn't nearly worth the complexity. That was why I decided not to bother with it. Supporting multiple run levels adds lots of complexity. Tools to change run levels, hooks into init, etc. Possibly a simpler system - "run states" - which aren't layered like the SysV run levels would provide most of the functionality without anywhere near the complexity. The state transitions are all from single-user (where rc.shutdown takes you) to and from different up states, using different pairs of directories to rc the system. In this case, the K* and S* filenames make more sense, so there's only one directory per state. This would handle the notebook, and anything that required some set of services to be turned on from single-user mode for maintenance. and my favorite substitute proposal: http://www.roguetrader.com/~brandon/sas/. Having working code makes it a lot more attractive than any of the others - or what we've discussed here. It's also a lot more complex that what we've been discussing. If you're willing to work on getting this integrated into the core, cool. If not - then I'd still like to see something that is easier to configure and deals with startup/shutdown issues better. Thanx, mike P.S. - anyone else remember rc.single? Anyone care? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Me too (was: Current Spontaneous Reboot)
On Monday, 10 July 2000 at 11:01:51 -0700, Thomas Dean wrote: I just experienced a sudden reboot. I am running -current SMP. Cvsup, make world, rebuild kernel 2709. # uname -a FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #0: \ Sun Jul 9 18:05:19 PDT 2000 \ root@celebris:/usr/src/sys/compile/CELEBRIS-SMP i386 # physical address: 0x0009fc30 # signature:'_MP_' # length: 16 bytes On Tuesday, 11 July 2000 at 1:47:10 +0200, Leif Neland wrote: Just a "me too" While telnetting to another machine, I suddenly got a "Page not present in supervisor mode", and a reference to rc5des. Unfortunately I hit the "any-key" too fast to provide any more info. On Tuesday, 11 July 2000 at 10:15:35 +0900, Noriyoshi Kawano wrote: Me too. But not SMP. Yet another "me too". I was in X at the time, so I didn't see any error messages. The sources were supped at 2030 UTC on Saturday, 8 July. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current Spontaneous Reboot
Noriyoshi Kawano wrote: Me too. But not SMP. Likewise. -current as of about an hour ago, no SMP, lotsa ram, buildworld about 3 hours ago. I saw no console because it was running X. - dmesg kernel trap 9 with interrupts disabled Fatal trap 9: general protection fault while in kernel mode instruction pointer = 0x8:0xc030ada4 stack pointer = 0x10:0xcb6b1c30 frame pointer = 0x10:0xcb6b1c80 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 3 current process = 298 (XF86_SVGA.xtt) interrupt mask = trap number = 9 panic: general protection fault syncing disks... 78 Fatal double fault: eip = 0xc02d8bfd esp = 0xcb6afffc ebp = 0xcb6b0090 panic: double fault Uptime: 1h20m34s To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Me too (was: Current Spontaneous Reboot)
Me too, kernel trap 9 with interrupts disabled Fatel trap 9: general protection fault while in kernel mode instruction pointer =0x8:0xc029f304 stack pointer =0x10:0xc3d97c30 frame pointer =0x10:0xc3d97c80 code segment=base 0x0, limit 0xf, type 0x1b =DPL 0, pres1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 13207 (as) interrupt mask = trap number = 9 panic: general protection fault #uname -a FreeBSD web4.allunix.com 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Mon Jul 10 21:55:05 PDT 2000 The system was cvsup'd and installed less then six hours ago. It is a non-smp system This is the second time, with both happening while building a program. *** REPLY SEPARATOR *** On 7/11/00 at 12:47 PM Greg Lehey wrote: On Monday, 10 July 2000 at 11:01:51 -0700, Thomas Dean wrote: I just experienced a sudden reboot. I am running -current SMP. Cvsup, make world, rebuild kernel 2709. # uname -a FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #0: \ Sun Jul 9 18:05:19 PDT 2000 \ root@celebris:/usr/src/sys/compile/CELEBRIS-SMP i386 # physical address: 0x0009fc30 # signature:'_MP_' # length: 16 bytes To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
