From owner-freebsd-current@FreeBSD.ORG Wed Apr 14 09:29:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A514516A4CE for ; Wed, 14 Apr 2004 09:29:36 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 6F24043D41 for ; Wed, 14 Apr 2004 09:29:34 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 83516 invoked by uid 1000); 14 Apr 2004 16:29:35 -0000 Date: Wed, 14 Apr 2004 09:29:35 -0700 (PDT) From: Nate Lawson To: stijn@win.tue.nl In-Reply-To: <20040414.001039.116586661.imp@bsdimp.com> Message-ID: <20040414092553.F83452@root.org> References: <20040414051207.GK58667@pcwin002.win.tue.nl> <20040413222717.O80191@root.org> <20040414.001039.116586661.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi@freebsd.org cc: current@freebsd.org Subject: Re: Experiences with new PCI code X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 14 Apr 2004 16:29:36 -0000 On Wed, 14 Apr 2004, M. Warner Losh wrote: > In message: <20040414054152.GL58667@pcwin002.win.tue.nl> > Stijn Hoop writes: > : On Tue, Apr 13, 2004 at 10:27:46PM -0700, Nate Lawson wrote: > : > On Wed, 14 Apr 2004, Stijn Hoop wrote: > : > > On Tue, Apr 13, 2004 at 09:23:39PM -0700, Nate Lawson wrote: > : > > > The other major issue that I can't ever solve is drivers not correctly > : > > > resuming themselves. That is up to the driver authors and a lot are > : > > > incomplete. > : > > > : > > Is there a list somewhere so that we end users don't report lots of > : > > known problems? > : > > : > That's item one on the list: make a list. Care to start one? :) > : > : Errrr... Can I tell by reading / grepping the source? > > Typically no. You tell because on your otherwise working laptop, the > Foo device doesn't resume. Yep. You can grep for drivers that don't have device_suspend in their methods list. But most have one. The usual case is that the suspend method is incomplete for some chipsets although it works ok on others. For instance, snd_ich works pretty well for me but will stop generating interrupts if shared with if_an on resume. But for others its sample rate is off after resume. Now this problem may have been fixed by Warner's power code so it would be a good time to test those drivers because if the problem is still there, it's a driver problem and there's not much more to be done outside the driver. -Nate