Date: Thu, 15 Apr 2004 13:36:49 -0700 (PDT) From: Nate Lawson <nate@root.org> To: Mark Santcroos <marks@ripe.net> Cc: current@freebsd.org Subject: Re: Experiences with new PCI code Message-ID: <20040415133527.G92275@root.org> In-Reply-To: <20040415135755.GA925@laptop.6bone.nl> References: <20040414051207.GK58667@pcwin002.win.tue.nl> <20040413222717.O80191@root.org><20040414092553.F83452@root.org> <20040415135755.GA925@laptop.6bone.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 15 Apr 2004, Mark Santcroos wrote: > 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. So you're saying your system doesn't stay in S3 but immediately wakes up even with the latest -current? Try commenting out all callers to acpi_enable_wake*(), including in acpi_lid, etc. Perhaps a premature wake event is being triggered. -Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040415133527.G92275>