From owner-freebsd-current@FreeBSD.ORG Thu Apr 19 00:48:12 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E050516A409 for ; Thu, 19 Apr 2007 00:48:12 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id 8943813C46E for ; Thu, 19 Apr 2007 00:48:12 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l3J0m9mb002331; Wed, 18 Apr 2007 20:48:11 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 18 Apr 2007 17:19:56 -0400 User-Agent: KMail/1.9.4 References: <20070401204942.GA14445@roadrunner.q.local> In-Reply-To: <20070401204942.GA14445@roadrunner.q.local> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200704181719.56592.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]); Wed, 18 Apr 2007 20:48:11 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.1 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00, DATE_IN_PAST_03_06 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Subject: Re: intsmb fails to attach X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Apr 2007 00:48:13 -0000 On Sunday 01 April 2007 16:49, Ulrich Spoerlein wrote: > Hi, > > I just upgraded my oldish ASUS P2B machine to current, and noticed > intsmb0 failing to attach. It's not that I need it, but perhaps the > problem is more wide spread: Did it work before? > intsmb0: port 0xe800-0xe80f at device 4.3 on pci0 > intsmb0: intr IRQ 9 enabled revision 0 > intsmb0: Unsupported interrupt mode > device_attach: intsmb0 attach returned 6 > > intsmb0@pci0:4:3: class=0x068000 card=0x00000000 chip=0x71138086 rev=0x02 hdr=0x00 > vendor = 'Intel Corporation' > device = '82371AB/EB/MB PIIX4/4E/4M Power Management Controller' > class = bridge > > Any stuff I should try? > > There are also some ACPI reservations failing, but as this is an old > board, I think this is to be expected: > > ACPI: RSDP @ 0x0xf7f80/0x0014 (v 0 ASUS ) > ACPI: RSDT @ 0x0x13ffd000/0x002C (v 1 ASUS P2B 0x42302E31 MSFT 0x31313031) > ACPI: FACP @ 0x0x13ffd080/0x0074 (v 1 ASUS P2B 0x42302E31 MSFT 0x31313031) > ACPI: DSDT @ 0x0x13ffd100/0x1BA8 (v 1 ASUS P2B 0x00001000 MSFT 0x01000001) > ACPI: FACS @ 0x0x13fff000/0x0040 > ACPI: BOOT @ 0x0x13ffd040/0x0028 (v 1 ASUS P2B 0x42302E31 MSFT 0x31313031) > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > acpi0: reservation of 100000, 13f00000 (3) failed > > Ulrich Spoerlein -- John Baldwin