Date: Mon, 15 Jan 2001 15:23:25 -0700 From: Janie Dykes <jkn33@pangeatech.com> To: Thierry Herbelot <thierry.herbelot@free.fr> Cc: hackers@freebsd.org Subject: Re: What to do if a box is just "frozen" Message-ID: <3A63785D.15B95577@pangeatech.com> References: <3A63732B.B92D7DDD@free.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
Thierry - I have a 4.1 Release box that seems to mimic your 'freezing' encounter. I seem to run into the same thing after having my box up for long periods of time and especially after using anything that requires bpf0. I've wondered if it was just an error in the kernel I compiled, or unusual network activity or the result of bad RAM or a physical hardware problem. I would love to know if anyone else has encountered this oddity. Any feedbak would be appreciated - Janie Thierry Herbelot wrote: > Hello, > > I've got a little application at work which can "just freeze" a > 4.2-Release : the purpose of the application is just a packet blaster > used for telecom equipement test (send as many UDP packets as ordered, > on as many interfaces as there are on a machine). > > So, on my 4.2-R test box (no-thrills BX, P-III 700 intel box), I have > some tens (around 30 of them) of such processes sending their packets, > and after some time (I have to more precisely determine this "some > time"), the box simply locks. > I do not see any message on console. > > I have connected a real keyboard (the box was connected to a KVM > switch), I have DDB enabled in the kernel, and the box is still freezing > (if it were at least panicing, this would be a good start) : I can't > jump with ctrl-alt-esc to DDB (even Ctrl-Alt-Del does not reboot the > machine). > > The memory does not seem to be a problem, as there are around 50 free > megabytes (out of 128), if top is to be believed (the box does not run > anything else than the blaster). the kernel is compiled with 8192 Mbuf > clusters (runs of netstat -m give a use of around 400 out of the 8192 > clusters) > > the "freezing" happens when the blaster is run as root, and also happens > when run as a casual user. > > the box has a reset button, but this obvioulsy erases any data in > memory. > > Is there something I could do to debug this problem ? (is there any way > to force a crash dump, via a serial console perhaps ? what is really > depressing is the loss of control from the keyboard, not being able to > switch to DDB) > > I will try to upgrade the boxes to a more recent -Stable, to see if the > problem still exists. > > TIA for any idea > > -- > Thierry Herbelot > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A63785D.15B95577>