From owner-freebsd-bugs@FreeBSD.ORG Wed Dec 3 15:07:58 2003 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0AD7C16A4CE for ; Wed, 3 Dec 2003 15:07:58 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC44F43FA3 for ; Wed, 3 Dec 2003 15:07:56 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id CF1E565339; Wed, 3 Dec 2003 23:07:54 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 85474-01-2; Wed, 3 Dec 2003 23:07:54 +0000 (GMT) Received: from saboteur.dek.spc.org (unknown [82.147.19.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id 56FDC652FE; Wed, 3 Dec 2003 23:07:54 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id 545BC3F; Wed, 3 Dec 2003 23:07:53 +0000 (GMT) Date: Wed, 3 Dec 2003 23:07:52 +0000 From: Bruce M Simpson To: Oliver Fischer Message-ID: <20031203230752.GA33193@saboteur.dek.spc.org> References: <200311251433.hAPEXmpb005578@freefall.freebsd.org> <3FCD28D9.6010806@snafu.de> <20031203000813.GB337@saboteur.dek.spc.org> <3FCE6B72.6000404@snafu.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FCE6B72.6000404@snafu.de> cc: freebsd-bugs@freebsd.org Subject: Re: kern/53481: 5.1R does not recognise xl0 at every startup X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2003 23:07:58 -0000 On Thu, Dec 04, 2003 at 12:02:10AM +0100, Oliver Fischer wrote: > Bruce M Simpson wrote: > >Were you using APM or ACPI? > > I used APM. Try disabling 'PCI power management' in the ThinkPad BIOS and see if that has an effect. The issue doesn't appear to be with the driver; sometimes Windows will place the card in the S3 ACPI power state and it loses some of its PCI configuration when this happens. BMS