From owner-freebsd-current Sun Feb 10 14:39:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NetScum.dyndns.dk (dclient217-162-168-31.hispeed.ch [217.162.168.31]) by hub.freebsd.org (Postfix) with ESMTP id 0181C37B419 for ; Sun, 10 Feb 2002 14:39:18 -0800 (PST) Received: from beerswilling.netscum.dyndns.dk (dcf77-zeit.netscum.dyndns.dk [172.27.72.27] (may be forged)) by dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NetScum.dyndns.dk (8.11.6/8.11.6) with ESMTP id g1AMdDr00244 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified FAIL) for ; Sun, 10 Feb 2002 23:39:17 +0100 (CET) (envelope-from bounce@dcf77-zeit.netscum.dyndns.dk) Received: (from root@localhost) by beerswilling.netscum.dyndns.dk (8.11.6/8.11.6) id g1AMdDH00243; Sun, 10 Feb 2002 23:39:13 +0100 (CET) (envelope-from bounce@dcf77-zeit.netscum.dyndns.dk) Date: Sun, 10 Feb 2002 23:39:13 +0100 (CET) Message-Id: <200202102239.g1AMdDH00243@beerswilling.netscum.dyndns.dk> From: BOUWSMA Beery To: freebsd-current@freebsd.org Subject: Minor things: swi_net: unregistered isr number Organization: Men not wearing any pants that dont shave X-Hacked: via telnet to your port 25, what else? X-Internet-Access-Provided-By: Mountain Informatik AG, Zuerich X-NetScum: Yes X-One-And-Only-Real-True-Fluffy: No Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If this might be of interest: kernel built 07.feb at boot time... | Doing initial network setup: hostname. * swi_net: unregistered isr number: 18. | xl0: flags=8843 mtu 1500 | options=3 [...] This is (probably) the dhclient being run at this time, maybe. Should I be bothered by the following? unknown: can't assign resources unknown: can't assign resources unknown: <16550 compatible COM device> can't assign resources unknown: <16550 compatible COM device> can't assign resources unknown: can't assign resources unknown: can't assign resources this is after all of these have been detected and assigned (sio0, sio1, etc) ata3: at port 0x36e-0x36f,0x168-0x16f irq 10 o n isa0 Where did that come from, and why don't I know about it? I know about: ata0 at port 0x3f6,0x1f0-0x1f7 irq 14 on isa0 ata1 at port 0x376,0x170-0x177 irq 15 on isa0 and -stable makes no claim I have a third ata controller... machine is ancient digital venturis 575 pc thanks barry bouwsma To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message