Date: Thu, 20 Jan 2005 23:01:35 -0500 From: Bryan Fullerton <fehwalker@gmail.com> To: freebsd-net@freebsd.org Subject: Re: em0 and pci interrupt routing? Message-ID: <35de0c30050120200116ab87d8@mail.gmail.com> In-Reply-To: <35de0c3005011305585b2a83f8@mail.gmail.com> References: <35de0c3005011305585b2a83f8@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <fehwalker@gmail.com> 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: <ACPI PCI bus> on pcib0 > pcib1: <ACPI PCI-PCI bridge> at device 3.0 on pci0 > pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.P0P2 > - AE_NOT_FOUND > pci1: <ACPI PCI bus> on pcib1 > em0: <Intel(R) PRO/1000 Network Connection, Version - 1.7.35> 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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?35de0c30050120200116ab87d8>