From owner-freebsd-hackers@FreeBSD.ORG Sun May 11 15:56:55 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB27A37B401 for ; Sun, 11 May 2003 15:56:55 -0700 (PDT) Received: from foem.leiden.webweaving.org (fia224-72.dsl.hccnet.nl [62.251.72.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEA1D43FEA for ; Sun, 11 May 2003 15:56:49 -0700 (PDT) (envelope-from dirkx@webweaving.org) Received: from foem (IDENT:chuckwebweaving.org@foem [10.11.0.2]) h4BMumv7031973 for ; Mon, 12 May 2003 00:56:48 +0200 (CEST) (envelope-from dirkx@webweaving.org) Date: Mon, 12 May 2003 00:56:48 +0200 (CEST) From: Dirk-Willem van Gulik X-X-Sender: dirkx@foem To: freebsd-hackers@freebsd.org Message-ID: <20030512005003.I14032-100000@foem> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: wi(4)/mini-PCI senao / not always initialized on boot. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 May 2003 22:56:56 -0000 With a mini-PCI formfactor wi(4) card (Senao) I am seeing wi0: mem 0xa0000000-0xa0000fff irq 10 at device 16.0 on pci0 wi0: CSR_READ_2(WI_HFA384X_SWSUPPORT0_OFF) wanted 18989, got 65535 device_probe_and_attach: wi0 attach returned 6 on roughly 4 out of very 5 reboots. A few extra reboot/powercycles seems to get me past it. Long/short/cold/warm resets or reboots seem not to clearly affect when one gets through successfully. I already tried adding some of the COR reset code (bit 7) to the native PCI branch in wi_pci_attach() but to no avail sofar. Any suggestion as to what this might be - and/or where I should look ? Thanks, Dw