From owner-freebsd-current@FreeBSD.ORG Tue Mar 8 16:57:54 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C00116A4CE for ; Tue, 8 Mar 2005 16:57:54 +0000 (GMT) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66C2543D53 for ; Tue, 8 Mar 2005 16:57:54 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtp (Exim 4.44 (FreeBSD)) id 1D8i1p-0004vL-S1; Tue, 08 Mar 2005 16:57:54 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com.psg.com) by roam.psg.com with esmtp (Exim 4.44 (FreeBSD)) id 1D8i1o-00035t-5P; Tue, 08 Mar 2005 06:57:52 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16941.55695.87991.238422@roam.psg.com> Date: Tue, 8 Mar 2005 06:57:51 -1000 To: othermark References: <1107887237.793.26.camel@buffy.york.ac.uk> <20050305020343.GO31320@elvis.mu.org> <16937.62150.818165.837486@roam.psg.com> cc: freebsd-current@freebsd.org Subject: Re: fxp0 and vlan panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Mar 2005 16:57:54 -0000 >> Fatal trap 12: page fault while in kernel mode >> fault virtual address = 0x80808517 >> fault code = supervisor read, page not present >> instruction pointer = 0x8:0xc047d2d0 >> stack pointer = 0x10:0xd3f78c88 >> frame pointer = 0x10:0xd3f78cac >> code segment = base 0x0, limit 0xfffff, type 0x1b >> = DPL 0, pres 1, def32 1, gran 1 >> processor eflags = interrupt enabled, resume, IOPL = 0 >> current process = 15 (irq5: fxp0) >> [thread pid 15 tid 100008 ] >> Stopped at fxp_intr_body+0xd0: cmpw $0,0(%esi) >> db> trace >> Tracing pid 15 tid 100008 td 0xc155fb80 >> fxp_intr_body(c161a000,c161a000,40,ffffffff,c0630cb6) at >> fxp_intr_body+0xd0 fxp_intr(c161a000,0,0,0,0) at fxp_intr+0x141 >> ithread_loop(c1551a00,d3f78d48,0,0,0) at ithread_loop+0x1a8 >> fork_exit(c04da530,c1551a00,d3f78d48) at fork_exit+0x7f >> fork_trampoline() at fork_trampoline+0x8 >> --- trap 0x1, eip = 0, esp = 0xd3f78d7c, ebp = 0 --- > > Hmm, can you get the panic to occur when interrupt coalescing is > turned on? 'ifconfig fxp0 link0' the panic is rare, takes a week or two to happen. so it is hard to know if changing to interrupt coalescing will fix. but i will try it after a while; as i am testing mux's latest patch kit right now. but thanks for the clue! randy