Bug 133985 - [kernel] kern.cp_time returns all zeros and stops incrementing on some hardware
Summary: [kernel] kern.cp_time returns all zeros and stops incrementing on some hardware
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-25 00:50 UTC by cmb
Modified: 2018-01-03 05:13 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description cmb 2009-04-25 00:50:03 UTC
We use kern.cp_time to calculate CPU usage, and a number of users are reporting problems. 

Sometimes kern.cp_time returns all zeros for periods of time. Sometimes it works to a point, 30-45 minutes or so, then stops incrementing and doesn't do so again until the system is rebooted. 

Most of the systems exhibiting this behavior are 440BX Pentium II motherboards. They worked fine in a FreeBSD 6.2-based pfSense release and stopped working after upgrading to 7.0 or 7.1-based releases. Some output from kern.cp_time here:
http://cvstrac.pfsense.org/tktview?tn=1884,0

This definitely seems like a hardware-specific regression from 6.2 to 7.0 and 7.1. Not sure what other information might be helpful, I'm glad to help obtain anything that may help.  Thanks

How-To-Repeat: Boot 7.0 or 7.1 on an affected system and wait 30-45 minutes and the cp_time values will stop incrementing. 

Run it repeatedly and you'll see all zeros being returned at times on affected hardware.
Comment 1 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:00:01 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped