Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!darwin.sura.net!paladin.american.edu!news.univie.ac.at!fstgds15.tu-graz.ac.at!fstgds15.tu-graz.ac.at!schinagl
From: schinagl@fstgds15.tu-graz.ac.at (Hermann Schinagl)
Newsgroups: comp.os.386bsd.questions
Subject: 'telnet localhost' causes reboot
Date: 20 Apr 1993 16:55:51 GMT
Organization: Technical University of Graz, Austria
Lines: 41
Message-ID: <1r19unINNmdi@fstgds15.tu-graz.ac.at>
NNTP-Posting-Host: fstgds15.tu-graz.ac.at
X-Newsreader: TIN [version 1.1 PL9]
I have discovered some strange behaviour on my 386bsd:
Typing 'telnet localhost' causes my system to reboot, but anything
seems to be configured well. There is no Ethernet interface in my computer.
The problem seems to be inside 'connect', so have tracked connect
through the kernel via printf and ddb:
connect ()
.
. instructions ...
.
soconnect()
.
tcp_usrreq()
.
I have set a breakpoint at the end of tcp_usrreq with ddb, and started
stepping at this point. The 'ret' of tcp_usrreq is ok, but there is a
normal instruction in 'sonewcon1()' ( or something similar ), which
causes ddb and the kernel to lock up, and perform a reboot.
The kernel works fine on a friends 386bsd, ( but he has an ethernet interface
plugged into his 386bsd ) and vice versa his kernels, reboots my system.
My knowledge about kernel interals is tooooo small, to find this bug, so
Someone had similar problems ???
Hardware: 486/DX2 66Mhz VLB, 16Mb Ram , Seagate 3138, no ethernet interface
Software: patchkit 0.2.2,
syscons ( but syscons is not the reason, I have tried it out )
we0, inet, nfs and X compiled in.
--
Ciao Hermann