From owner-freebsd-current@FreeBSD.ORG Mon Mar 7 16:11:07 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 DF2D916A4CE for ; Mon, 7 Mar 2005 16:11:07 +0000 (GMT) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4E8943D46 for ; Mon, 7 Mar 2005 16:11:06 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1D8KiX-0001Ij-36 for freebsd-current@freebsd.org; Mon, 07 Mar 2005 17:04:25 +0100 Received: from mulder.f5.com ([205.229.151.150]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 07 Mar 2005 17:04:24 +0100 Received: from atkin901 by mulder.f5.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 07 Mar 2005 17:04:24 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: othermark Date: Mon, 07 Mar 2005 08:09:54 -0800 Lines: 39 Message-ID: References: <1107887237.793.26.camel@buffy.york.ac.uk> <20050226120253.O87543@ury.york.ac.uk> <20050305020343.GO31320@elvis.mu.org> <16937.62150.818165.837486@roam.psg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: mulder.f5.com User-Agent: KNode/0.8.2 Sender: news X-Gmane-MailScanner: Found to be clean X-Gmane-MailScanner: Found to be clean X-MailScanner-From: freebsd-current@m.gmane.org X-MailScanner-To: 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: Mon, 07 Mar 2005 16:11:08 -0000 Randy Bush wrote: >> Just for the record, and for people not reading CVS commit logs, I >> committed a fix for this a few days ago and I will make sure to MFC >> it in time for 5.4-RELEASE. > > might this give me some help on occasional but repeated fxp > crashes under load? > > 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' I've loaded my -current boxes pretty hard and have not seen this panic, but I have interrupt coalescing turned on everywhere. -- othermark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired);