Date: Fri, 7 Dec 2007 21:46:37 +0200 From: Nikolay Pavlov <qpadla@gmail.com> To: Erik Trulsson <ertr1013@student.uu.se> Cc: freebsd-current@freebsd.org Subject: Re: Strange IRQ number Message-ID: <200712072146.37458.qpadla@gmail.com> In-Reply-To: <20071207192642.GA65135@owl.midgard.homeip.net> References: <200712072114.01360.qpadla@gmail.com> <20071207192642.GA65135@owl.midgard.homeip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart1795797.neeHdfm7lH Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 07 December 2007 21:26:42 Erik Trulsson wrote: > On Fri, Dec 07, 2007 at 09:13:57PM +0200, Nikolay Pavlov wrote: > > I see some strange IRQ number for my em0 card on BETA4: > > root@cassini:~# vmstat -i > > interrupt total rate > > irq1: atkbd0 6 0 > > irq6: fdc0 1 0 > > irq14: ata0 184947 16 > > irq15: ata1 184946 16 > > cpu0: timer 22110598 1999 > > irq256: em0 6945039 628 > > ^^^^^^^^^^^^^^^^ > > cpu1: timer 22110396 1999 > > Total 51535933 4661 > > > > On 6.2 it was shared with uhci. Now all uhci controllers gone from the > > vmstat but not from the system: > > 'vmstat -i' only shows those interrupts that have generated at least one > interrupt. Use 'vmstat -ia' to see all the interrupts (I suspect that > you will find the uhci* devices there.) > > > root@cassini:~# usbdevs > > addr 1: UHCI root hub, Intel > > addr 1: UHCI root hub, Intel > > addr 1: UHCI root hub, Intel > > addr 1: UHCI root hub, Intel > > addr 1: EHCI root hub, Intel > > > > root@cassini:~# dmesg | grep em0 > > em0: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port > > 0x4000-0x401f mem 0xd0100000-0xd011ffff irq 16 at device 0.0 on pci6 > > em0: Using MSI interrupt > > ^^^^^^^^^^^^^^^^^^^^^^ > > This is the magic information. On 7.x MSI/MSI-X interrupts are enabled > by default (which is not the case on 6.x). > MSI/MSI-X is a new interrupt delivery mechanism that can be used by all > PCI-E devices (although not all device drivers in FreeBSD take > advantage of this yet) and some PCI-X devices, that essentially assigns > a separate interrupt for each device - thus no need for sharing > interrupts. > > > em0: Ethernet address: 00:30:48:91:c0:90 > > em0: [FILTER] > > > > The entire system work ok. > > As expected. What you see is simply the em0 NIC (apparently a PCI-E > device) using MSI instead of the old interrupt method. > FreeBSD assigns such devices a "virtual" interrupt number starting at > 256. > > > Short version: It is not a bug, it is a feature. :-) Yes you are right Erik. Thanks for a good explanation. :) =2D-=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 =2D Best regards, Nikolay Pavlov. <<<----------------------------------- = =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 --nextPart1795797.neeHdfm7lH Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBHWaMd/2R6KvEYGaIRAmpiAJ9Ro2T6AxcEOr44frNh8P98MhhHKwCg8tKh NHUkBKqyM8Vr1oC9p1HuHY0= =uXRA -----END PGP SIGNATURE----- --nextPart1795797.neeHdfm7lH--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200712072146.37458.qpadla>