From owner-freebsd-current@FreeBSD.ORG Thu Apr 15 12:04:32 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 D65A516A4CE; Thu, 15 Apr 2004 12:04:32 -0700 (PDT) Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id D275543D41; Thu, 15 Apr 2004 12:04:31 -0700 (PDT) (envelope-from marks@dell-laptop.6bone.nl) Received: by postman.ripe.net (Postfix, from userid 8) id E17BB51CA6; Thu, 15 Apr 2004 21:04:28 +0200 (CEST) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id A0EAA4FF58; Thu, 15 Apr 2004 21:04:28 +0200 (CEST) Received: from dell-laptop.6bone.nl (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.10/8.11.6) with SMTP id i3FJ4Sc4020766; Thu, 15 Apr 2004 21:04:28 +0200 Received: (nullmailer pid 993 invoked by uid 1001); Thu, 15 Apr 2004 13:57:55 -0000 Date: Thu, 15 Apr 2004 15:57:55 +0200 From: Mark Santcroos To: Nate Lawson Message-ID: <20040415135755.GA925@laptop.6bone.nl> References: <20040414051207.GK58667@pcwin002.win.tue.nl> <20040413222717.O80191@root.org> <20040414.001039.116586661.imp@bsdimp.com> <20040414092553.F83452@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040414092553.F83452@root.org> User-Agent: Mutt/1.4.2.1i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Level: X-RIPE-Spam-Status: U 0.251308 / 0.2 / 0.0 / disabled X-RIPE-Signature: f8e90f28024b2131b934d1635cd330af 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: Thu, 15 Apr 2004 19:04:33 -0000 On Wed, Apr 14, 2004 at 09:29:35AM -0700, Nate Lawson wrote: > 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. My laptop was one of those with the snd_ich problems after S4_BIOS resume. It was caused by bad BAR restores as the problem could be fixed by simply setting the PCI registers as they were before suspend. I can acknowledge that it now works without any twiddling. Listening to some music right now after I have just suspended :-) Like said before, the PCI changes didn't have any influence on my "S3 immediate resume after suspend" issue. Mark