Date: Mon, 15 Mar 2004 17:12:02 +0100 From: "Roderick van Domburg" <r.s.a.vandomburg@student.utwente.nl> To: <freebsd-sparc64@freebsd.org> Subject: 64-bTT isc-dhcp3-client experiences Message-ID: <200403151612.i2FGC0619559@netlx014.civ.utwente.nl>
next in thread | raw e-mail | index | archive | help
Hello everyone, Just completed the upgrade and my system seems to run fine, with the exception of DHCP. I installed the isc-dhcp3-client port as instructed, and recompiled it using a 64-bTT, but here's some unexpected behavior: dhclient gets an initial lease, everything seems to be peachy. As observed earlier, the lease renewal times in /var/db/dhclient.leases are totally off. Restarting dhclient flips its behavior from reporting a year like 823423423 between 2004 - 20xx. However, after a minute or two dhclient starts releasing and renewing like there's no tomorrow, peaking CPU usage of both itself and syslogd. The system becomes completely unusable. Anyone else noticed this behavior? Running isc-dhclient-V3.0.1rc12 and a March 15 world. A dmesg and KERNCONF follow, the system is a Sun Enterprise 250. Regards, Roderick --8<--- dmesg --8<--- Copyright (c) 1992-2004 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.2-CURRENT #0: Mon Mar 15 11:51:36 CET 2004 roderick@magog.student.utwente.nl:/usr/obj/usr/src/sys/MAGOG Preloaded elf kernel "/boot/kernel/kernel" at 0xc02e8000. Timecounter "tick" frequency 400000000 Hz quality 0 real memory = 536870912 (512 MB) avail memory = 509575168 (485 MB) cpu0: Sun Microsystems UltraSparc-II Processor (400.00 MHz CPU) nexus0: <OpenFirmware Nexus device> nexus0: <associations>, type (unknown) (no driver attached) pcib0: <U2P UPA-PCI bridge> on nexus0 pcib0: Psycho, impl 0, version 4, ign 0x7c0, bus B pcib0: [FAST] pcib0: [FAST] pcib0: [FAST] initialializing counter-timer Timecounter "counter-timer" frequency 1000000 Hz quality 0 DVMA map: 0xfc000000 to 0xffffffff pci0: <OFW PCI bus> on pcib0 ebus0: revision 0x01 ebus0: <PCI-EBus2 bridge> mem 0x71000000-0x717fffff,0x70000000-0x70ffffff at device 1.0 on pci0 ebus0: <auxio> addr 0x140072f000-0x140072f003,0x140072c000-0x140072c003,0x140072a000-0x140072a00 3,0x1400728000-0x1400728003,0x1400726000-0x1400726003 (no driver attached) ebus0: <power> addr 0x1400724000-0x1400724003 (no driver attached) ebus0: <SUNW,pll> addr 0x1400504000-0x1400504002 (no driver attached) ebus0: <sc> addr 0x1400500000-0x1400500007 (no driver attached) ebus0: <se> addr 0x1400400000-0x140040007f irq 43 (no driver attached) ebus0: <se> addr 0x1400200000-0x140020007f irq 35 (no driver attached) ebus0: <su> addr 0x14003083f8-0x14003083ff irq 41 (no driver attached) ebus0: <su> addr 0x14003062f8-0x14003062ff irq 33 (no driver attached) ebus0: <ecpp> addr 0x1400700000-0x140070000f,0x1400300398-0x1400300399,0x14003043bc-0x14003043c b irq 33 (no driver attached) eeprom0: <EBus EEPROM/clock> addr 0x1400000000-0x1400001fff on ebus0 eeprom0: model mk48t59 eeprom0: hostid 80cfc01b ebus0: <flashprom> addr 0x1000000000-0x10000fffff,0x1000000000-0x10000fffff (no driver attached) ebus0: <SUNW,envctrltwo> addr 0x1400600000-0x1400600003 irq 37,40 (no driver attached) hme0: <Sun HME 10/100 Ethernet> mem 0x4100000-0x4107fff at device 1.1 on pci0 hme0: Ethernet address: 08:00:20:cf:c0:1b miibus0: <MII bus> on hme0 nsphy0: <DP83840 10/100 media interface> on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto hme0: Ethernet address: 08:00:20:cf:c0:1b sym0: <875> port 0x2000-0x20ff mem 0x410a000-0x410afff,0x4108000-0x41080ff at device 3.0 on pci0 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking sym1: <875> port 0x2400-0x24ff mem 0x410e000-0x410efff,0x410c000-0x410c0ff at device 3.1 on pci0 sym1: No NVRAM, ID 7, Fast-20, SE, parity checking pcib1: <OFW PCI-PCI bridge> at device 2.0 on pci0 pci1: <OFW PCI bus> on pcib1 hme1: <Sun HME 10/100 Ethernet> mem 0x4000000-0x4007fff at device 0.1 on pci1 pcib1: slot 0 INTB is routed to irq 17 hme1: Ethernet address: 08:00:20:cf:c0:1b miibus1: <MII bus> on hme1 ukphy0: <Generic IEEE 802.3u media interface> on miibus1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto hme1: Ethernet address: 08:00:20:cf:c0:1b pci1: <mass storage, SCSI> at device 4.0 (no driver attached) pcib2: <U2P UPA-PCI bridge> on nexus0 pcib2: Psycho, impl 0, version 4, ign 0x7c0, bus A pci2: <OFW PCI bus> on pcib2 pci2: <display> at device 1.0 (no driver attached) nexus0: <rsc>, type system-service-processor (no driver attached) nexus0: <mc>, type memory-controller (no driver attached) Timecounters tick every 10.000 msec Waiting 15 seconds for SCSI devices to settle da0 at sym0 bus 0 target 0 lun 0 da0: <FUJITSU MAG3091L SUN9.0G 1111> Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da0: 8637MB (17689267 512 byte sectors: 255H 63S/T 1101C) da2 at sym0 bus 0 target 9 lun 0 da2: <FUJITSU MAE3091L SUN9.0G 0706> Fixed Direct Access SCSI-2 device da2: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da2: 8637MB (17689267 512 byte sectors: 255H 63S/T 1101C) da1 at sym0 bus 0 target 8 lun 0 da1: <FUJITSU MAG3091L SUN9.0G 1111> Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da1: 8637MB (17689267 512 byte sectors: 255H 63S/T 1101C) da3 at sym0 bus 0 target 10 lun 0 da3: <FUJITSU MAB3091S SUN9.0G 2107> Fixed Direct Access SCSI-2 device da3: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da3: 8637MB (17689267 512 byte sectors: 255H 63S/T 1101C) da5 at sym0 bus 0 target 12 lun 0 da5: <FUJITSU MAB3091S SUN9.0G 2107> Fixed Direct Access SCSI-2 device da5: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da5: 8637MB (17689267 512 byte sectors: 255H 63S/T 1101C) da4 at sym0 bus 0 target 11 lun 0 da4: <FUJITSU MAB3091S SUN9.0G 2107> Fixed Direct Access SCSI-2 device da4: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da4: 8637MB (17689267 512 byte sectors: 255H 63S/T 1101C) Mounting root from ufs:/dev/da0a ipfw2 initialized, divert disabled, rule-based forwarding enabled, default to deny, logging disabled --8<--- KERNCONF --8<--- # # MAGOG -- Sun Enterprise 250 kernel configuration file for FreeBSD/sparc64 # machine sparc64 cpu SUN4U ident MAGOG options SCHED_ULE #ULE scheduler options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options UFS_DIRHASH #Improve performance on big directories options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI 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 extensions # Standard busses device ebus device pci # New OpenFirmware PCI framework. This fixes a number of interrupt- # routing problems and changes the device enumeration to be hopefully # closer to Solaris. Be aware that, because of the latter, enabling or # disabling this option may require reconfiguration, and can even # cause the machine to not boot without manual intervention before the # fstab is adjusted. options OFW_NEWPCI # SCSI Controllers device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') # SCSI peripherals device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) device ofw_console # OpenBoot firmware console device # Builtin hardware device genclock # Generic clock interface device eeprom # eeprom (really an ebus driver for the MK48Txx) device "mk48txx" # Mostek MK48T02, MK48T08, MK48T59 clock # PCI Ethernet NICs that use the common MII bus controller code. device miibus # MII bus support device hme # Sun HME (Happy Meal Ethernet) # Pseudo devices - the number indicates how many units to allocated. device random # Entropy device device loop # Network loopback device ether # Ethernet support device pty # Pseudo-ttys (telnet etc) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf #Berkeley packet filter # RANDOM_IP_ID causes the ID field in IP packets to be randomized # instead of incremented by 1 with each packet generated. This # option closes a minor information leak which allows remote # observers to determine the rate of packet generation on the # machine by watching the counter. options RANDOM_IP_ID
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200403151612.i2FGC0619559>