Date: Wed, 29 Dec 2004 00:20:10 +0100 From: Andrea Campi <andrea+acpi@webcom.it> To: John Baldwin <jhb@FreeBSD.org> Cc: freebsd-acpi@FreeBSD.org Subject: Re: S3 experience on Thinkpad 570E Message-ID: <20041228232009.GC90171@webcom.it> In-Reply-To: <200412281027.58052.jhb@FreeBSD.org> References: <20041223145047.GA1064@webcom.it> <41D0931F.2010200@root.org> <200412281027.58052.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 28, 2004 at 10:27:57AM -0500, John Baldwin wrote:
> > > 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.
OK, thanks. Just for completeness, I'll check and report what
happens with a different value of HZ (100, for instance ;-)), just in
case this makes any difference--as I would expect if this is a case
of resuming to some hardcoded value.
Bye,
Andrea
--
The dark ages were caused by the Y1K problem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041228232009.GC90171>