FreeBSD 5.1-Release freezes
Hi all I have just installed 5.1 Release on my laptop (6gb harddisk and 60 mb ram). I only installed the base system + man pages and the port collection. A little info: / 128M Swap256M /var128M /var/tmp 256M (/tmp is symlinked to this) /home 256M /usrThe rest I compiled a new kernel, with no support for SCSI, RAID, IPv6 and all but my USB NIC (also removed a few USB things). I added: options SC_DISABLE_REBOOT options MAC device pcm It compiled fine and I installed it. Now, if I run with this kernel the system freezes! I can boot, login and run a few commands, but that's it. There is nothing in the logs, but when I tried ssh'ing to the mashine I got this before it froze: fork() - Not enough ressources available at this time (or something like that). Is there a memory leak somewhere or am I doing something wrong? (I compiled and installed the kernel with: make buildkernel KERNCONF=SOCKETD make installkernel KERNCONF=SOCKETD) btw please cc to me as I am not on the list. br socketd ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 5.1-Release freezes
On Wed, 25 Jun 2003 10:24:43 -0700
"Kevin Oberman" <[EMAIL PROTECTED]> wrote:
> Providing your complete configuration file and /var/run/dmesg.boot
> might give a bit of a clue.
Ok. /usr/src/sys/i386/conf/SOCKETD:
machine i386
cpu I586_CPU
ident SOCKETD
options SCHED_4BSD #4BSD scheduler
options INET#InterNETworking
options FFS #Berkeley Fast Filesystem
options SOFTUPDATES #Enable FFS soft updates support
options UFS_ACL #Support for access control
lists
options UFS_DIRHASH #Improve performance on big
directories
options MD_ROOT #MD is a potential root device
options MSDOSFS #MSDOS Filesystem
options CD9660 #ISO 9660 Filesystem
options PROCFS #Process filesystem (requires
PSEUDOFS)
options PSEUDOFS#Pseudo-filesystem framework
options COMPAT_43 #Compatible with BSD 4.3 [KEEP
THIS!]
options COMPAT_FREEBSD4 #Compatible with FreeBSD4
options SCSI_DELAY=15000#Delay (in ms) before probing
SCSI
options KTRACE #ktrace(1) support
options SYSVSHM #SYSV-style shared memory
options SYSVMSG #SYSV-style message queues
options SYSVSEM #SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time
extensionsoptions KBD_INSTALL_CDEV# install a CDEV entry
in /dev
options AHC_REG_PRETTY_PRINT# Print register bitfields in
debug
# output. Adds ~128k to driver.
options AHD_REG_PRETTY_PRINT# Print register bitfields in
debug
# output. Adds ~215k to driver.
options INVARIANT_SUPPORT #Extra sanity checks of internal
structures, required by INVARIANTS
device isa
device eisa
device pci
device fdc
device ata
device atadisk # ATA disk drives
device atapicd # ATAPI CDROM drives
device atapifd # ATAPI floppy drives
device atapist # ATAPI tape drives
options ATA_STATIC_ID #Static device numbering
device atkbdc # AT keyboard controller
device atkbd # AT keyboard
device psm # PS/2 mouse
device vga # VGA video card driver
device splash # Splash screen and screen saver support
device sc
device agp # support several AGP chipsets
device npx
device pmtimer
device cbb # cardbus (yenta) bridge
device pccard # PC Card (16-bit) bus
device cardbus # CardBus (32-bit) bus
device sio # 8250, 16[45]50 based serial ports
device ppc
device ppbus # Parallel port bus (required)
device lpt # Printer
device plip# TCP/IP over parallel
device ppi # Parallel port interface device
device miibus # MII bus support
device random # Entropy device
device loop# Network loopback
device ether # Ethernet support
device tun # Packet tunnel.
device pty # Pseudo-ttys (telnet etc)
device md # Memory "disks"
device bpf # Berkeley packet filter
device uhci# UHCI PCI->USB interface
device ohci# OHCI PCI->USB interface
device usb # USB Bus (required)
device ugen# Generic
device uhid# "Human Interface Devices"
device ukbd# Keyboard
device ums # Mouse
device aue # ADMtek USB ethernet
device pcm
options SC_DISABLE_REBOOT
options MAC
And /var/run/dmesg.boot
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-RELEASE #1: Sat Jan 2 03:46:39 CET 1999
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SOCKETD
Preloaded elf kernel "/boot/kernel/kernel" at 0xc048f000.
Preloaded elf module "/boot/kernel/acpi.ko" at 0xc048f1f4.
Timecounter "i8254" frequency 1193182 Hz
Timecounter "TSC" frequency 448341906 Hz
CPU: AMD-K6(tm) 3D processor (448.34-MHz 586-class CPU)
Origin = "AuthenticAMD" Id = 0x58c Steppi
Re: FreeBSD 5.1-Release freezes
On Wed, 25 Jun 2003 16:44:56 -0400 (EDT) Robert Watson <[EMAIL PROTECTED]> wrote: > Sounds like a memory leak to me; it might also be a locking problem. > Are you actually running with any MAC policies, or just with the > framework? Just the framework, no policies. > The code most likely to cause a memory leak in the MAC Framework is > the label management code, since that's the only code that really does > much in the way of memory allocaiton. Try compiling options MAC_DEBUG > into your kernel, which causes the MAC Framework to track the number > of labels it has allocated/free'd in a series of variables: [snip] Ok, I will try and do the things du suggest (never tried that before), but am I the only one with this problem? If you'd like, I can give you root access to the laptop, then you can play all you want :-) br socketd ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 5.1-Release freezes
On Wed, 25 Jun 2003 16:44:56 -0400 (EDT) Robert Watson <[EMAIL PROTECTED]> wrote: > The code most likely to cause a memory leak in the MAC Framework is > the label management code, since that's the only code that really does > much in the way of memory allocaiton. Try compiling options MAC_DEBUG > into your kernel, which causes the MAC Framework to track the number > of labels it has allocated/free'd in a series of variables: > > static unsigned int nmacmbufs, nmaccreds, nmacifnets, nmacbpfdescs, > nmacsockets, nmacmounts, nmactemp, nmacvnodes, nmacdevfsdirents, > nmacipqs, nmacpipes, nmacprocs; > > You can inspect them using a series of sysctls in the > security.mac.debug tree; I'd be interested to see how those values > change as you approach the hang. Hmm, this is strange. I build the same kernel with: makeoptions DEBUG=-g options DDB #Enable the kernel debugger options INVARIANTS #Enable calls of extra sanity checking options INVARIANT_SUPPORT #Extra sanity checks of internal structures, required by INVARIANTS options WITNESS #Enable checks to detect deadlocks and cycles options MAC options MAC_DEBUG Now it doesn't hang and there is nothing in the logs. Btw here is some info: security.mac.debug.label_fallback: 0 security.mac.debug.counters.mbufs: 0 security.mac.debug.counters.creds: 17 security.mac.debug.counters.ifnets: 3 security.mac.debug.counters.ipqs: 0 security.mac.debug.counters.bpfdescs: 0 security.mac.debug.counters.sockets: 7 security.mac.debug.counters.pipes: 2 security.mac.debug.counters.procs: 63 security.mac.debug.counters.mounts: 6 security.mac.debug.counters.temp: 0 security.mac.debug.counters.vnodes: 429 security.mac.debug.counters.devfsdirents: 96 Again I am not running anything but the base system and ssh. br socketd ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 5.1-Release freezes
On Wed, 25 Jun 2003 16:44:56 -0400 (EDT) Robert Watson <[EMAIL PROTECTED]> wrote: > The code most likely to cause a memory leak in the MAC Framework is > the label management code, since that's the only code that really does > much in the way of memory allocaiton. Try compiling options MAC_DEBUG > into your kernel, which causes the MAC Framework to track the number > of labels it has allocated/free'd in a series of variables: > > static unsigned int nmacmbufs, nmaccreds, nmacifnets, nmacbpfdescs, > nmacsockets, nmacmounts, nmactemp, nmacvnodes, nmacdevfsdirents, > nmacipqs, nmacpipes, nmacprocs; After running a few commands, ssh logins and loading mac_seeotheruids we now have: security.mac.debug.label_fallback: 0 security.mac.debug.counters.mbufs: 0 security.mac.debug.counters.creds: 17 security.mac.debug.counters.ifnets: 3 security.mac.debug.counters.ipqs: 0 security.mac.debug.counters.bpfdescs: 0 security.mac.debug.counters.sockets: 7 security.mac.debug.counters.pipes: 2 security.mac.debug.counters.procs: 63 security.mac.debug.counters.mounts: 6 security.mac.debug.counters.temp: 0 security.mac.debug.counters.vnodes: 524 security.mac.debug.counters.devfsdirents: 99 Loading mac_seeotheruids made vnodes increase a little, but it has (very slowly) been increasing and as you can see is now at 524 (don't know if this means anything). br socketd ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Gateway/Networking problems in FreeBSD 5.1-Release
Hi all I have a computer with 3 NIC's (10/100) and I am trying to set it up as a gateway. In /etc/rc.conf I have: ifconfig_rl1="inet 192.168.1.22 netmast 255.255.255.0 media 100baseTX" ifconfig_de0="inet 192.168.1.21 netmast 255.255.255.0 media 100baseTX" ifconfig_rl0="inet 192.168.1.20 netmast 255.255.255.0 media 100baseTX" When booting I get: rl0: port 0xc800-0xc8ff mem 0xea001000-0xea0010ff irq 9 at device 9.0 on pci0 rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode rl0: Ethernet address: 00:e0:7d:98:7a:a4 de0: port 0xcc00-0xcc7f mem 0xea00-0xea7f irq 12 at device 10.0 on pci0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:a0:cc:66:8d:73 de0: enabling 100baseTX port de0: link down: cable problem? rl1: port 0xd000-0xd0ff mem 0xea002000-0xea0020ff irq 5 at device 11.0 on pci0 rl1: Realtek 8139B detected. Warning, this may be unstable in autoselect mode rl1: Ethernet address: 00:00:e8:71:6e:89 When running ifconfig I get: rl0: flags=8843 mtu 1500 inet 192.168.1.20 netmask 0xff00 broadcast 192.168.1.255 ether 00:e0:7d:98:7a:a4 media: Ethernet 100baseTX status: active de0: flags=8843 mtu 1500 ether 00:a0:cc:66:8d:73 media: Ethernet 100baseTX status: no carrier rl1: flags=8843 mtu 1500 ether 00:00:e8:71:6e:89 media: Ethernet 100baseTX status: no carrier lp0: flags=8810 mtu 1500 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff00 Only rl0 works. With rl0 I can sniff my LAN, but not connect (ping) to any computers. Another problem is that rl0 and rl1 (I am not testing de0 jet) have status: no carrier after booting. I have to take out and plug in the network cable in order to make them active. Please CC to me as I am not on the list :-) br socketd ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Gateway/Networking problems in FreeBSD 5.1-Release
On Thu, 3 Jul 2003 06:34:10 -0700 (PDT) David Wolfskill <[EMAIL PROTECTED]> wrote: > OK; this is not a -current issue. Maybe -questions I thought it might be a 5.X problem > That makes no sense whatsoever. By having more than one NIC on your > machine, you make it multi-homed. A multi-homed machine is connected > to multiple networks -- one for each NIC -- except under rather > unusual circumstances (involving "spanning tree" algorithms). I was just testing the NIC's, not making the final setup. > See what happens when you assign network numbers and IP addresses > sanely. Ok, I chose 192.168.1.11, 192.168.2.11 and 192.168.3.11 and now it is working (strange it can't work with IP's is the same netmask), but I still have to unplug and plug the nic cable to get it active!?!? br socketd ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
