Date: Tue, 28 Dec 2004 10:27:57 -0500 From: John Baldwin <jhb@FreeBSD.org> To: Nate Lawson <nate@root.org> Cc: freebsd-acpi@FreeBSD.org Subject: Re: S3 experience on Thinkpad 570E Message-ID: <200412281027.58052.jhb@FreeBSD.org> In-Reply-To: <41D0931F.2010200@root.org> References: <20041223145047.GA1064@webcom.it> <41D0931F.2010200@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 27 December 2004 05:56 pm, Nate Lawson wrote: > Andrea Campi wrote: > > Hi, > > > > I've tried using S3 on -CURRENT, more in response to Nate's request than > > out of need, since S4BIOS is working great on this PC. > > > > In a nutshell, acpiconf -s3 powers down; on powerup however the machine > > is deadly slow. I replicated this with a stripped down kernel; the only > > thing that was evidently wrong is that the clock slowed down from 1000 to > > around 250 interrupts per second. > > It sounds like the clock interrupt source is not getting saved/restored > properly if it slows after a resume. I am not sure how to solve this. > Perhaps John has something to add. Currently on i386 the clocks are not real new-bus devices and I'm not sure if they have proper resume support. I think we do have some sort of hardcoded call to the clock code on i386 to resume the clocks but I'm not sure. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200412281027.58052.jhb>