http://bugzilla.kernel.org/show_bug.cgi?id=12651





------- Comment #3 from [email protected]  2009-02-09 02:24 -------
BTW I'm running a 64bit kernel and I removed everything from the .config that I
consider unnecessary. Can the issue lie in my .config?

> From the /proc/timer_list it seems that the idle_sleep time on CPU0 is far 
> less than that on CPU1.

It is. I was surprised too when I saw that. Though there was no load in the
system at the moment (I stopped all unneded daemons).

$ ps auxww
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.2  0.0   3624   576 ?        Ss   12:09   0:00 init [2]  
root         2  0.0  0.0      0     0 ?        S<   12:09   0:00 [kthreadd]
root         3  0.0  0.0      0     0 ?        S<   12:09   0:00 [migration/0]
root         4  0.0  0.0      0     0 ?        S<   12:09   0:00 [ksoftirqd/0]
root         5  0.0  0.0      0     0 ?        S<   12:09   0:00 [migration/1]
root         6  0.0  0.0      0     0 ?        S<   12:09   0:00 [ksoftirqd/1]
root         7  0.0  0.0      0     0 ?        S<   12:09   0:00 [events/0]
root         8  0.0  0.0      0     0 ?        S<   12:09   0:00 [events/1]
root         9  0.0  0.0      0     0 ?        S<   12:09   0:00 [khelper]
root        10  0.0  0.0      0     0 ?        S<   12:09   0:00 [kstop/0]
root        11  0.0  0.0      0     0 ?        S<   12:09   0:00 [kstop/1]
root        12  0.0  0.0      0     0 ?        S<   12:09   0:00 [kblockd/0]
root        13  0.0  0.0      0     0 ?        S<   12:09   0:00 [kblockd/1]
root        14  0.0  0.0      0     0 ?        S<   12:09   0:00 [kacpid]
root        15  0.0  0.0      0     0 ?        S<   12:09   0:00 [kacpi_notify]
root        16  0.0  0.0      0     0 ?        S<   12:09   0:00 [ata/0]
root        17  0.0  0.0      0     0 ?        S<   12:09   0:00 [ata/1]
root        18  0.0  0.0      0     0 ?        S<   12:09   0:00 [ata_aux]
root        19  0.0  0.0      0     0 ?        S<   12:09   0:00
[ksuspend_usbd]
root        20  0.0  0.0      0     0 ?        S<   12:09   0:00 [khubd]
root        21  0.0  0.0      0     0 ?        S<   12:09   0:00 [kondemand/0]
root        22  0.0  0.0      0     0 ?        S<   12:09   0:00 [kondemand/1]
root        23  0.0  0.0      0     0 ?        S    12:09   0:00 [pdflush]
root        24  0.0  0.0      0     0 ?        S    12:09   0:00 [pdflush]
root        25  0.0  0.0      0     0 ?        S<   12:09   0:00 [kswapd0]
root        26  0.0  0.0      0     0 ?        S<   12:09   0:00 [scsi_eh_0]
root        27  0.0  0.0      0     0 ?        S<   12:09   0:00 [scsi_eh_1]
root        28  0.0  0.0      0     0 ?        S<   12:09   0:00 [scsi_eh_2]
root        29  0.0  0.0      0     0 ?        S<   12:09   0:00 [scsi_eh_3]
root        30  0.0  0.0      0     0 ?        S<   12:09   0:00 [kjournald]
root        38  0.0  0.0   5772   484 ?        S<s  12:09   0:00 udevd --daemon
root       364  0.0  0.0      0     0 ?        S<   12:09   0:00 [kjournald]
root       365  0.0  0.0      0     0 ?        S<   12:09   0:00 [kjournald]
root       390  0.0  0.0  32888  1040 tty1     Ss   12:09   0:00 /bin/login --  
root       391  0.0  0.0   3620   492 tty2     Ss+  12:09   0:00 /sbin/agetty
-I \033c\033[9;0]\033[11;0]\033(K 38400 tty2 linux
root       394  0.0  0.0   3620   496 tty4     Ss+  12:09   0:00 /sbin/agetty
-I \033c\033[9;0]\033[11;0]\033(K 38400 tty4 linux
pv        406  0.0  0.0  96124  1972 tty1     S    12:09   0:00 -bash
root       430  0.0  0.0   3620   496 tty3     Ss+  12:10   0:00 /sbin/agetty
-I \033c\033[9;0]\033[11;0]\033(K 38400 tty3 linux
pv        440  0.0  0.0  86804  1088 tty1     R+   12:10   0:00 ps auxww

With nohz=off highres=off (see below) timer_list is still "incorrect" but the
cpu speed is 1000 MHz as expected.

$ dmesg |grep nohz
Command line: BOOT_IMAGE=LinuxNOHZ ro root=802 nohz=off highres=off
Kernel command line: BOOT_IMAGE=LinuxNOHZ ro root=802 nohz=off highres=off

$ grep 1000 /proc/cpuinfo
cpu MHz         : 1000.000
cpu MHz         : 1000.000

$ cat /proc/timer_list
Timer List Version: v0.4
HRTIMER_MAX_CLOCK_BASES: 2
now at 82579990814 nsecs

cpu: 0
 clock 0:
  .base:       ffff880001014a78
  .index:      0
  .resolution: 3333116 nsecs
  .get_time:   <ffffffff802421f7>
active timers:
 clock 1:
  .base:       ffff880001014ab0
  .index:      1
  .resolution: 3333116 nsecs
  .get_time:   <ffffffff80242282>
active timers:
  .nohz_mode      : 0
  .idle_tick      : 0 nsecs
  .tick_stopped   : 0
  .idle_jiffies   : 0
  .idle_calls     : 0
  .idle_sleeps    : 0
  .idle_entrytime : 82579990814 nsecs
  .idle_waketime  : 0 nsecs
  .idle_exittime  : 0 nsecs
  .idle_sleeptime : 233332990 nsecs
  .last_jiffies   : 0
  .next_jiffies   : 0
  .idle_expires   : 0 nsecs
jiffies: 4294902070

cpu: 1
 clock 0:
  .base:       ffff88000101fa78
  .index:      0
  .resolution: 3333116 nsecs
  .get_time:   <ffffffff802421f7>
active timers:
 clock 1:
  .base:       ffff88000101fab0
  .index:      1
  .resolution: 3333116 nsecs
  .get_time:   <ffffffff80242282>
active timers:
 #0: <ffffffff8056de48>, <ffffffff802289c1>, S:01
 # expires at 83000000000-83000000000 nsecs [in 420009186 to 420009186 nsecs]
 #1: <ffff88007f837998>, <ffffffff80241a17>, S:01
 # expires at 86333324153-86338324153 nsecs [in 3753333339 to 3758333339 nsecs]
 #2: <ffff88007edd7ad8>, <ffffffff80241a17>, S:01
 # expires at 1805846657512-1805946657512 nsecs [in 1723266666698 to
1723366666698 nsecs]
  .nohz_mode      : 0
  .idle_tick      : 0 nsecs
  .tick_stopped   : 0
  .idle_jiffies   : 0
  .idle_calls     : 0
  .idle_sleeps    : 0
  .idle_entrytime : 82579990814 nsecs
  .idle_waketime  : 0 nsecs
  .idle_exittime  : 0 nsecs
  .idle_sleeptime : 81083325864 nsecs
  .last_jiffies   : 0
  .next_jiffies   : 0
  .idle_expires   : 0 nsecs
jiffies: 4294902070


Tick Device: mode:     0
Broadcast device
Clock Event Device: pit
 max_delta_ns:   27461866
 min_delta_ns:   12571
 mult:           5124677
 shift:          32
 mode:           1
 next_event:     9223372036854775807 nsecs
 set_next_event: <ffffffff80210f43>
 set_mode:       <ffffffff80210ed0>
 event_handler:  <ffffffff80245c31>
tick_broadcast_mask: 00000000
tick_broadcast_oneshot_mask: 00000000


Tick Device: mode:     0
Per CPU device: 0
Clock Event Device: lapic
 max_delta_ns:   668033311
 min_delta_ns:   1194
 mult:           53932629
 shift:          32
 mode:           2
 next_event:     9223372036854775807 nsecs
 set_next_event: <ffffffff8021a05a>
 set_mode:       <ffffffff8021a074>
 event_handler:  <ffffffff8024635d>

Tick Device: mode:     0
Per CPU device: 1
Clock Event Device: lapic
 max_delta_ns:   668033311
 min_delta_ns:   1194
 mult:           53932629
 shift:          32
 mode:           2
 next_event:     9223372036854775807 nsecs
 set_next_event: <ffffffff8021a05a>
 set_mode:       <ffffffff8021a074>
 event_handler:  <ffffffff8024635d>


-- 
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.

------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
acpi-bugzilla mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to