Date: Thu, 5 Oct 1995 10:15:37 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: wollman@lcs.mit.edu (Garrett A. Wollman) Cc: ccam@kudu.ru.ac.za, freebsd-questions@freebsd.org Subject: Re: tcpdump aborts Message-ID: <199510050045.KAA17426@genesis.atrad.adelaide.edu.au> In-Reply-To: <9510041511.AA26824@halloran-eldar.lcs.mit.edu> from "Garrett A. Wollman" at Oct 4, 95 11:11:58 am
next in thread | previous in thread | raw e-mail | index | archive | help
Garrett A. Wollman stands accused of saying: > There is nowhere near enough informatio to even begin to diagnose > this. You must provide the following information: > > Version of FreeBSD > Kernel configuration file > Exact `tcpdump' command line > All output generated by the panic > > You should use the `send-pr' command to submit this information as an > official problem report. Without this information, we cannot even > guess as to the cause of your problem. I'm going to be a naughty boy and not use send-pr for this one, mostly because I can't afford to reproduce it at the moment. I've seen the same symptom using tcpdump on a 'de' ethernet card (Compex). IIRC, it would have been 'tcpdump -l -e -f -i de0 -N -v' This is on 2.0.5-RELEASE, on a P100 Soyo Triton board. I was running X at the time, so I didn't get any of the trap details. If someone wants to make a time with me to check this one (if it's not known to be fixed), I can arrange to take the system offline. > -GAWollman -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510050045.KAA17426>