From owner-freebsd-net@FreeBSD.ORG Fri Jan 21 04:01:36 2005 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1811216A4CE for ; Fri, 21 Jan 2005 04:01:36 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEAC043D31 for ; Fri, 21 Jan 2005 04:01:35 +0000 (GMT) (envelope-from fehwalker@gmail.com) Received: by wproxy.gmail.com with SMTP id 63so138883wri for ; Thu, 20 Jan 2005 20:01:35 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=gkR5wW6DaV+zGgoCyh/f7R4Q/+EMqIIp9Tbaq7CgoSeOD4PVSVFy6hE1uBM++1rNt2NfVYiDtrC16x13cSzZFNZkmxbJGnn+Okp82ziXukuH69paN8ujY3CYDgQetbxRDMKv8aMDRGMbr3gbovv0N8QDlvG7cAxP/+QIcc33cQY= Received: by 10.54.19.17 with SMTP id 17mr31245wrs; Thu, 20 Jan 2005 20:01:35 -0800 (PST) Received: by 10.54.19.59 with HTTP; Thu, 20 Jan 2005 20:01:35 -0800 (PST) Message-ID: <35de0c30050120200116ab87d8@mail.gmail.com> Date: Thu, 20 Jan 2005 23:01:35 -0500 From: Bryan Fullerton To: freebsd-net@freebsd.org In-Reply-To: <35de0c3005011305585b2a83f8@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <35de0c3005011305585b2a83f8@mail.gmail.com> Subject: Re: em0 and pci interrupt routing? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Bryan Fullerton List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 04:01:36 -0000 FWIW, I updated from 5.3-RELEASE-p5 to 5.3-STABLE of 20050119 and am no longer seeing the "could not get PCI interrupt routing table" error noted below in dmesg. I'm unsure if this means the issue is gone or if it's just no longer logged. :/ The other issue I'm seeing (occasional sig11's with postfix's smtp client when there's moderate network and disk IO) still occurs. Thanks, Bryan On Thu, 13 Jan 2005 08:58:00 -0500, Bryan Fullerton wrote: > Howdy, > > I'm having some issues with a new server, and was wondering if the > interrupt routing message below could be indicating a problem that > needs investigation. > > pci0: on pcib0 > pcib1: at device 3.0 on pci0 > pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.P0P2 > - AE_NOT_FOUND > pci1: on pcib1 > em0: port > 0xcc00-0xcc1f mem 0xfb4e0000-0xfb4fffff irq 18 at device 1.0 on pci1 > em0: Ethernet address: 00:02:b3:ea:28:20 > em0: Speed:N/A Duplex:N/A > > The machine is using an Intel SE7210TP1-E motherboard, and the em0 > interface is onboard. I don't see any other PCI interrupt routing > messages in dmesg. > > Thanks, > Bryan >