More often than not, on a warm boot I see something like this msg.new:[ 1.940031] Using local APIC timer interrupts. msg.new:[ 1.944031] APIC timer calibration result 466046 msg.new:[ 1.944031] Detected 0.466 MHz APIC timer. msg.new:[ 1.944031] APIC frequency too slow, disabling apic timer On cold boots it may see 12.5MHz, or may not... [ 2.000584] Using local APIC timer interrupts. [ 2.004067] APIC timer calibration result 12500236 [ 2.004080] Detected 12.500 MHz APIC timer. I haven't figured out yet what the pattern is behind the behavior. Has anyone else seen this kind of problem before? -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/ --
| hooanon05 | [PATCH 67/67] merge aufs |
| Greg Kroah-Hartman | [PATCH 008/196] Chinese: add translation of volatile-considered-harmful.txt |
| monstr | [PATCH 33/52] [microblaze] bug headers files |
| Oliver Pinter | Re: x86: 4kstacks default |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| David Miller | [GIT]: Networking |
| Natalie Protasevich | [BUG] New Kernel Bugs |
