Date: Tue, 19 Dec 1995 16:27:23 -0500 (EST) From: "Marc G. Fournier" <scrappy@hub.org> To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= <ache@astral.msk.su> Cc: faried nawaz <nawaz921@cs.uidaho.edu>, current@freebsd.org Subject: Re: panic: m_copydata Message-ID: <Pine.BSF.3.91.951219160813.2068F-100000@hub.org> In-Reply-To: <HxePmrmiK5@ache.dialup.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 19 Dec 1995, =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= wrote: > In message <199512191505.HAA08739@hoodoo.cs.uidaho.edu> faried nawaz > writes: > > >"Marc G. Fournier" wrote... > > > Trace: > > > _Debugger(f0111fe0,f011d5e4,efbffe94,14) at _Debugger+0x2b > > _panic(f011d5e3,14,ffffffff,f05f3880,efbfff20) at _panic+0x3b > > _m_copydata(0,ffffffff,1,f05f38e8,0) at _m_copydata+0x21 > > _tcp_output(f05a4f00,f061169c,f0611b80,14,efbfff30) at > > _tcp_output+0x635 > > _tcp_input(f0611680,14) at _tcp_input+0x13da > > _ipintr(f0172117,0,efbf0027,27,3c) at _ipintr+0x429 > > Bad User Frame pointer: 0xefbf9120 > > I saw (and report) the same picture too... :-( > Okay...I got a response to this for more information, and what was asked for was: " Could you type `panic' in DDB next time you get this error to create a dump, and then print the contents of the `*tp' structure in the tcp_output() routine, and the contents of `*ti' in one frame up, in tcp_input(). " Now, to get my above trace, you have to have DDB enabled in the kernel, which will drop you to a "debug prompt" instead of rebooting the machine (neat feature if you happen to be around...just don't go away for the weekend *grin*) Just type 'tra' when it gets to that prompt, and it will give you exactly as above. To get the dump, you have to enable 'options DODUMP' in the kernel, and use 'config -g <conf-file>'. I'm assuming that to enable DDB, DODUMP has to be enabled first off, as I think they depend on each other. Then, in /etc/sysconfig, enable the following: # Set to the name of the device for kernel crashdumps, or `off' to # disable any statically configured dumpdev, or NO for no change. # The device should normally be one of the swap devices specified # in /etc/fstab. dumpdev=/dev/sd0b # Set to YES if you want kernel crashdumps to be saved for debugging savecore=YES And then, at the DDB prompt, type panic. Urm...make sure you have both a /var/crash directory, *and* there is enough disk space to write the core file to it (~= RAM size) Now...what to do with that core file? Check out Chapter 15 of the Handbook (found in /usr/share/doc/handbook...or, if you don't have it, I have it up at http://hub.org, as a link from the main page) That should be about all the information that I just received on how to help debug this problem...my *-current machine is down right now, and won't be up for a couple of days, so hopefully this helps track down the problem sooner... :) Marc G. Fournier | POP Mail Telnet Acct DNS Hosting scrappy@hub.org | WWW Services Database Services | Knowledge, soon to be: | | Information and scrappy@ki.net | WWW: http://hub.org | Communications, Inc
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.951219160813.2068F-100000>