From owner-freebsd-stable Tue Jan 25 16:43:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 63FB114D34 for ; Tue, 25 Jan 2000 16:43:04 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA03502; Tue, 25 Jan 2000 16:51:20 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001260051.QAA03502@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Bryan Bursey Cc: freebsd-stable@FreeBSD.ORG Subject: Re: IRQs appearing incorrectly in dmesg In-reply-to: Your message of "Tue, 25 Jan 2000 20:18:04 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Jan 2000 16:51:20 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > G'day folks... > > My 3.4-STABLE box is incorrectly reporting the IRQs for many of my PCI > devices in dmesg. Some details are inserted below. I'm wondering if > there's any way to determine the _actual_ IRQs or is there a dmesg issue > here. I'm using an Abit BP-6 mainboard. > > [bbursey@nipplehead bbursey]$ uname -a > FreeBSD nipplehead.yi.org 3.4-STABLE FreeBSD 3.4-STABLE #1: Sun Jan 23 > 05:05:39 AST 2000 root@:/usr/src/sys/compile/NIP_KERNEL i386 > > xl0: <3Com 3c900B-TPO Etherlink XL> rev 0x04 int a irq 19 on pci0.9.0 > es1: rev 0x01 int a irq 17 on pci0.13.0 > bktr0: rev 0x11 int a irq 16 on pci0.15.0 > > Any help and/or advice much appreciated. If this is an SMP system, the IRQ number is meaningless. This is why 4.x systems probably won't print them. (The number actually reflects the low-level interrupt handler in modern systems, and sort-of does in yours.) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message