Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!goanna.cs.rmit.edu.au!news.apana.org.au!cantor.edge.net.au!news.teragen.com.au!news.access.net.au!news.mel.connect.com.au!munnari.OZ.AU!uunet!in2.uu.net!205.152.0.23!news.atl.bellsouth.net!news.mia.bellsouth.net!celo.sodre.net!news From: cmwagner@nando.sodre.net (Chad Wagner) Newsgroups: comp.unix.bsd.freebsd.misc Subject: FreeBSD 2.1.7 rebooting Date: 8 Mar 1997 17:12:20 -0500 Organization: SodreNet Internet Services Lines: 61 Message-ID: <5fso84$44m@nando.sodre.net> NNTP-Posting-Host: nando.sodre.net Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:36783 I realize this was discussed at great length about a month ago, but apparently I missed the discussion, the box is rebooting on it's own, no messages, nothing. I am wondering what I can do to help tackle the problem, should I recompile the kernel with any of the debugging options, which ones? Probing for devices on PCI bus 0: chip0 <generic PCI bridge (vendor=%04x device=%04x subclass=%1.2d)> rev 1 on pci 0:0 chip1 <Intel 82371SB PCI-ISA bridge> rev 1 on pci0:7:0 chip2 <Intel 82371SB IDE interface> rev 0 on pci0:7:1 ncr0 <ncr 53c815 scsi> rev 3 int a irq 11 on pci0:17 ncr0 waiting for scsi devices to settle (ncr0:6:0): "CONNER CFP2105S 2.14GB 172A" type 0 fixed SCSI 2 sd0(ncr0:6:0): Direct-Access sd0(ncr0:6:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 2048MB (4194304 512 byte sectors) vga0 <VGA-compatible display device> rev 0 int a irq 10 on pci0:20 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 5 on isa ed0: address 00:40:95:2a:11:70, type NE2000 (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface changing root device to sd0a WARNING: / was not properly dismounted. in_rtqtimo: adjusted rtq_reallyold to 2400 in_rtqtimo: adjusted rtq_reallyold to 1600 in_rtqtimo: adjusted rtq_reallyold to 1066 in_rtqtimo: adjusted rtq_reallyold to 710 in_rtqtimo: adjusted rtq_reallyold to 473 in_rtqtimo: adjusted rtq_reallyold to 315 in_rtqtimo: adjusted rtq_reallyold to 210 in_rtqtimo: adjusted rtq_reallyold to 140 in_rtqtimo: adjusted rtq_reallyold to 93 What I am also wondering is what does rtq_reallyold mean? It sounds like by looking at the code that it is a routing table expiration time, and as the more the routing table gets filled the quicker it desires to expire, and probably eventually just expiring on the fly. The machine sees an extreme amount of network traffic. But I still can't figure out why it is crashing, we have also modified the kernel to support a larger number of client connections, by increasing maxusers to 128, OPEN_MAX=256, CHILD_MAX=256, FD_SETSIZE=4096, NMBCLUSTERS=6144 Any assistance would be greatly appreciated, I can be contacted via e-mail at cmwagner@sodre.net. -- || Chad Wagner Network/System Administrator || || cmwagner@sodre.net || cmwagner@oaktree.net || cmwagner@fountainauto.com ||