dhclient wedged

2006-02-02 Thread John T. Yocum 
I've been having a same sort of issue that others have reported. After 
dhclient has been running for a random length of time, it suddenly 
starts consuming a large amount of CPU. Unfortunately for me, the 
longest it tends to run is 48 hours before acting up.


I did get it rebuilt with debug symbols, and got a stack trace from it, 
while it was acting up. Hopefully, it will be useful.


Attaching to program: /sbin/dhclient, process 2248
Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /libexec/ld-elf.so.1...done.
Loaded symbols for /libexec/ld-elf.so.1
0x08051a0d in receive_packet (interface=0x8071000,
buf=0xbfbfdc20 \002\001\006, len=4096, from=0xbfbfec70, 
hfrom=0xbfbfec50)

at /usr/src/sbin/dhclient/bpf.c:308
308 memcpy(hdr, 
interface-rbuf[interface-rbuf_offset],

(gdb) bt
#0  0x08051a0d in receive_packet (interface=0x8071000,
buf=0xbfbfdc20 \002\001\006, len=4096, from=0xbfbfec70, 
hfrom=0xbfbfec50)

at /usr/src/sbin/dhclient/bpf.c:308
#1  0x08050dc1 in got_one (l=0x80741b0)
at /usr/src/sbin/dhclient/dispatch.c:256
#2  0x08050d58 in dispatch () at /usr/src/sbin/dhclient/dispatch.c:228
#3  0x0804a0d0 in main (argc=1, argv=0xbfbfed3c)
at /usr/src/sbin/dhclient/dhclient.c:429

BTW: For reference I'm running 6.0-RELEASE-p4.

Thanks,
John
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

kernel/dmesg misreporting clock speed of CPU

2005-05-04 Thread John T. Yocum 
Hello,
Just an update to my previous post about the clock speed being 
misreported. As of RC4, the clockspeed appears to be reported correctly.

Thanks,
John
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

kernel/dmesg misreporting clock speed of CPU

2005-04-22 Thread John T. Yocum 
Hello,
First off, want to say thanks to all the people that make FreeBSD 
possible. Very nice operating system. :) Ok, now for the problem.

Been running FreeBSD 5-STABLE on my Dual Pentium Pro 200Mhz for many 
months now. However, yesterday I upped to 5.4-RC3, and noticed something 
changed during bootup.

This line:
CPU: Pentium Pro (145.59-MHz 686-class CPU)
Note that line says 145.59-Mhz, I have 200Mhz CPUs. As well, prior to 
upgrading to RC-3 that line would say 199.98Mhz. Not sure if that's a 
bug or not.

Here's my dmesg output, wasn't sure if this would be needed:
Copyright (c) 1992-2005 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.4-RC3 #3: Wed Apr 20 07:49:53 PDT 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/KOALA
MPTable: HP   LH Pro  
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Pentium Pro (145.59-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x619  Stepping = 9
Features=0xfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV
real memory  = 234881024 (224 MB)
avail memory = 224391168 (213 MB)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  1
 cpu1 (AP): APIC ID:  0
ioapic0: Assuming intbase of 0
ioapic0 Version 1.1 irqs 0-15 on motherboard
npx0: math processor on motherboard
npx0: INT 16 interface
cpu0 on motherboard
cpu1 on motherboard
pcib0: Host to PCI bridge pcibus 0 on motherboard
pci0: PCI bus on pcib0
pcib1: PCI-PCI bridge at device 8.0 on pci0
pci1: PCI bus on pcib1
xl0: 3Com 3c905-TX Fast Etherlink XL port 0xecc0-0xecff irq 9 at 
device 2.0 on pci1
miibus0: MII bus on xl0
nsphy0: DP83840 10/100 media interface on miibus0
nsphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
xl0: Ethernet address: 00:10:4b:d1:5d:f4
xl1: 3Com 3c905-TX Fast Etherlink XL port 0xec40-0xec7f irq 10 at 
device 3.0 on pci1
miibus1: MII bus on xl1
nsphy1: DP83840 10/100 media interface on miibus1
nsphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
xl1: Ethernet address: 00:60:97:c9:af:7b
eisab0: PCI-EISA bridge at device 9.0 on pci0
eisa0: EISA bus on eisab0
mainboard0: HWPc141 (System Board) on eisa0 slot 0
isa0: ISA bus on eisab0
ahc0: Adaptec aic7880 Ultra SCSI adapter port 0xf800-0xf8ff mem 
0xfedff000-0xfedf irq 11 at device 10.0 on pci0
ahc0: Using left over BIOS settings
aic7880: Wide Channel A, SCSI Id=7, 16/253 SCBs
ahc1: Adaptec aic7880 Ultra SCSI adapter port 0xf400-0xf4ff mem 
0xfedfe000-0xfedfefff irq 11 at device 11.0 on pci0
ahc1: Using left over BIOS settings
aic7880: Wide Channel A, SCSI Id=7, 16/253 SCBs
orm0: ISA Option ROMs at iomem 0xc8000-0xcbfff,0xc-0xc7fff on isa0
pmtimer0 on isa0
atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0
atkbd0: AT Keyboard irq 1 on atkbdc0
kbd0 at atkbd0
fdc0: Enhanced floppy controller at port 0x3f0-0x3f5 irq 6 drq 2 on isa0
fd0: 1440-KB 3.5 drive on fdc0 drive 0
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x300
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
unknown: PNP0501 can't assign resources (port)
unknown: PNP0501 can't assign resources (port)
unknown: PNP0700 can't assign resources (port)
unknown: PNP0303 can't assign resources (port)
unknown: PNP0903 can't assign resources (memory)
unknown: PNP0c02 can't assign resources (memory)
Timecounters tick every 10.000 msec
Waiting 5 seconds for SCSI devices to settle
da0 at ahc0 bus 0 target 0 lun 0
da0: IBM DXHS18Y 0430 Fixed Direct Access SCSI-3 device
da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing 
Enabled
da0: 17366MB (35566480 512 byte sectors: 64H 32S/T 17366C)
da1 at ahc0 bus 0 target 1 lun 0
da1: IBM DXHS18Y 0430 Fixed Direct Access SCSI-3 device
da1: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing 
Enabled
da1: 17366MB (35566480 512 byte sectors: 64H 32S/T 17366C)
da2 at ahc0 bus 0 target 3 lun 0
da2: HP 2.13 GB 1st ### 1221 Fixed Direct Access SCSI-2 device
da2: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing 
Enabled
da2: 2033MB (4165272 512 byte sectors: 64H 32S/T 2033C)
SMP: AP CPU #1 Launched!
cd0 at ahc0 bus 0 target 5 lun 0
cd0: TOSHIBA CD-ROM XM-5401TA 3115 Removable CD-ROM SCSI-2 device
cd0: 4.032MB/s transfers (4.032MHz, offset 15)
cd0: Attempt to query device size failed: NOT READY, Medium not present
Mounting root from ufs:/dev/da0s1a
pflog0: promiscuous mode enabled
xl1: transmission error: 90
xl1: tx underrun, increasing tx start threshold to 120 bytes
xl0: transmission error: 90
xl0: tx underrun, increasing tx start threshold to 120 bytes
xl0: transmission error: 90
xl0: tx underrun, increasing tx start threshold to 180 bytes
xl0: transmission error: 90
xl0: tx underrun, increasing tx start threshold to 240

Re: kernel/dmesg misreporting clock speed of CPU

2005-04-22 Thread John T. Yocum 
Jon Noack wrote:
On 4/22/2005 9:07 AM, John T. Yocum wrote:
First off, want to say thanks to all the people that make FreeBSD 
possible. Very nice operating system. :) Ok, now for the problem.

Been running FreeBSD 5-STABLE on my Dual Pentium Pro 200Mhz for many 
months now. However, yesterday I upped to 5.4-RC3, and noticed 
something changed during bootup.

This line:
CPU: Pentium Pro (145.59-MHz 686-class CPU)
Note that line says 145.59-Mhz, I have 200Mhz CPUs. As well, prior to 
upgrading to RC-3 that line would say 199.98Mhz. Not sure if that's a 
bug or not.

Random shot:
BIOS battery died and the speed got reset to 150MHz?
Then again, the speed on the Pentium Pro machine I used to have was set 
with a jumper (had it overclocked to 233MHz!)...

Sorry if I'm way off base here,
Jon
Jon,
The clockspeed is setup via jumpers. Just before rebooting to RC3, the 
kernel was reporting the proper clock speed. IIRC, this issue has come 
up before for some people.

Thanks,
John
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]