From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 8634] New: Unstable clocksource reported
Date: Fri, 15 Jun 2007 13:36:46 -0700 (PDT) [thread overview]
Message-ID: <bug-8634-3570@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=8634
Summary: Unstable clocksource reported
Product: Power Management
Version: 2.5
KernelVersion: 2.6.21.5
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
AssignedTo: cpufreq@www.linux.org.uk
ReportedBy: patrick.matthaei@web.de
Most recent kernel where this bug did not occur: Not known
Distribution: Debian Sid
Hardware Environment: AMD Athlon64 San Diego 4000+
Software Environment: Tickless Timer Support (64bit CPU, but 32bit system)
Problem Description:
Every time if I activate the 'ondemand' powersave gorvener, dmesg reports
following:
Time: acpi_pm clocksource has been installed.
Clocksource tsc unstable (delta = -245560788 ns)
This thing needs at booting up ~ 2-10 seconds, which is a lot of time, so I
think this is a bug.
My kernel config with all my inbuilded powersave features etc. is in attached.
Steps to reproduce:
Just do a "/bin/echo 'ondemand' >
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor".
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-06-15 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 20:36 bugme-daemon [this message]
2007-06-15 20:37 ` [Bug 8634] Unstable clocksource reported bugme-daemon
2007-06-16 7:05 ` bugme-daemon
2007-06-18 1:16 ` bugme-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-8634-3570@http.bugzilla.kernel.org/ \
--to=bugme-daemon@bugzilla.kernel.org \
--cc=cpufreq@www.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.