Date: Tue, 23 Nov 2004 10:31:02 +0800 From: Ganbold <ganbold@micom.mng.net> To: Robert Watson <rwatson@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: Page fault in FreeBSD 5.3 on IBM e325, Dual AMD64 2.2GHz, 4GB RAM, ServeRAID 6M - debug logs Message-ID: <6.2.0.14.2.20041123102644.03040770@202.179.0.80> In-Reply-To: <Pine.NEB.3.96L.1041122104130.19086Q-100000@fledge.watson.o rg> References: <6.2.0.14.2.20041122151958.0303be20@202.179.0.80> <Pine.NEB.3.96L.1041122104130.19086Q-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 06:43 PM 11/22/2004, you wrote: >On Mon, 22 Nov 2004, Ganbold wrote: > > > Fatal trap 12: page fault while in kernel mode > > cpuid = 1; apic id = 01 > > fault virtual address = 0x18 > > fault code = supervisor read, page not present > > instruction pointer = 0x8:0xffffffff80277fc0 > > stack pointer = 0x10:0xffffffffb36ab830 > > frame pointer = 0x10:0xffffffffb36ab890 > > code segment = base 0x0, limit 0xfffff, type 0x1b > > = DPL 0, pres 1, long 1, def32 0, gran 1 > > processor eflags = interrupt enabled, resume, IOPL = 0 > > current process = 44 (swi1: net) > > [thread 100044] > > Stopped at m_copym+0x190: incl %ecx ><...> > > > -------------------------------------------------------------------------------------------------------- > > > > It seems to me the problem is related to network stack and threading. > > Am I right? How to solve this problem? > >I've seen reports of this problem with and without debug.mpsafenet=1, >which suggests it is a network stack bug but not specific to locking. I've >also seen reports that disabling TCP SACK will make the problem go away, >which would be good to confirm. I spent the weekend building up some more >expertise in TCP and reading a lot of TCP code, and hope to look at this >problem in more detail today. You may want to try turning off TCP sack >using net.inet.tcp.sack.enable=0 in sysctl.conf (or loader.conf). Thanks Robert. I will try as you suggested and let you know. Please let me know if you find the fix to this problem later on. thanks, Ganbold >Robert N M Watson FreeBSD Core Team, TrustedBSD Projects >robert@fledge.watson.org Principal Research Scientist, McAfee Research > > >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.2.0.14.2.20041123102644.03040770>