Date: Tue, 1 Jun 2004 10:54:35 -0400 (EDT) From: Robert Watson <rwatson@freebsd.org> To: Divacky Roman <xdivac02@stud.fit.vutbr.cz> Cc: current@freebsd.org Subject: Re: uipc_socket2.c panic Message-ID: <Pine.NEB.3.96L.1040601105243.98063B-100000@fledge.watson.org> In-Reply-To: <20040601082954.GA49773@stud.fit.vutbr.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 1 Jun 2004, Divacky Roman wrote: > I am getting panics in uipc_socket2.c very often (every hour at least). > I am afraid I am not able to provide you more info since I dont have -g > compiled kernel and it takes me more than hour to compile kernel on this > machine ;( > > once the panic was on line 867, then it was 885 > > necrophilia kern# uname -a > FreeBSD necrophilia 5.2-CURRENT FreeBSD 5.2-CURRENT #90: Tue Jun 1 > 09:15:45 CES > T 2004 root@necrophilia:/usr/obj/usr/src/sys/NEOLOGISM i386 > necrophilia kern# > > (ie, mbuma kernel) > > roman > > P.S. I am deeply sorry for not providing more Even without symbols, the panic message and trap information would be very useful. If it's a page fault, having the instruction pointer and faulting address would allow us to make some headway. If it's a panic(), the panic string and instruction pointer would likewise be extremely useful. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1040601105243.98063B-100000>