On Mon, Apr 30, 2007 at 11:38:34PM +0200, Thomas Gleixner wrote:
> On Mon, 2007-04-30 at 18:39 +0200, Joerg Sommrey wrote:
> > Here it is. Maybe this problem is related to the usage of the
> > "experimental" amd76x_pm module?
>
> Can you please verify what happens w/o that module ?
>
After rebooting the problem vanished for now. It first appeared after
an uptime of about 3 days. I'll wait a few days. If it shows
again, then I'll check without amd76x_pm.
-jo
> Thanks,
>
> tglx
>
>
--
-rw-r--r-- 1 jo users 62 2007-05-01 01:11 /home/jo/.signature
On Tue, May 01, 2007 at 09:36:24AM +0200, Joerg Sommrey wrote:
> On Mon, Apr 30, 2007 at 11:38:34PM +0200, Thomas Gleixner wrote:
> > On Mon, 2007-04-30 at 18:39 +0200, Joerg Sommrey wrote:
> > > Here it is. Maybe this problem is related to the usage of the
> > > "experimental" amd76x_pm module?
> >
> > Can you please verify what happens w/o that module ?
> >
> After rebooting the problem vanished for now. It first appeared after
> an uptime of about 3 days. I'll wait a few days. If it shows
> again, then I'll check without amd76x_pm.
It really looks like amd76x_pm is causing the time loss. Sadly, I have
no idea how to avoid this. What happens when the pm-timer wraps around
while the processors are in C3 sleep state? How is this wrap detected
at all? Is there anything I could put into amd76x_pm? It's no problem
detecting a timer wrap there.
-jo
--
-rw-r--r-- 1 jo users 62 2007-05-13 21:55 /home/jo/.signature