Processor - idle missing

[kim1963]

Updated from hrev47738 to hrev47748. CPU usage is zero. The cooling fan operates at the limit. Exhausting air is very hot. On hrev47738 - all right!

Kernel name: kernel_x86 built on: Aug 24 2014 17:04:07 version 0x1
4 Intel Core™ i3-2330M, revision 206a7 running at 2195MHz

CPU #0: "Intel(R) Core(TM) i3-2330M CPU @ 2.20GHz"
Raw CPUID: 0x0206a7, Type 0, family 6, model 42, stepping 7, features 0xbfebfbff
FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT
PSE36 CFLUSH DS ACPI MMX FXSTR SSE SSE2 SS HTT TM PBE
Extended Intel: 0x15bae3bf
SSE3 PCLMULDQ DTES64 MONITOR DS-CPL VMX EST TM2 SSSE3 CX16 xTPR PDCM PCID SSE4.1 SSE4.2 x2APIC
POPCNT TSC-DEADLINE XSAVE AVX
Extended AMD: type 0, family 0, model 0, stepping 0, features 0x28100000
NX RDTSCP 64
Power Management Features:

L2 Data cache fully associative, 1 lines/tag, 64 bytes/line
L2 cache: 0 KB, 1-way set associative, 0 lines/tag, 63 bytes/line

Data TLB: 2M/4M-bytes pages, 4-way set associative, 32 entries
Data TLB: 4k-byte pages, 4-way set associative, 64 entries
Unknown cache descriptor 0x76
Unknown cache descriptor 0xff
Inst TLB: 4K-bytes pages, 4-way set associative, 64 entries
64-byte Prefetching
Shared 2nd-level TLB: 4K, 4-way set associative, 512 entries

[diver]

Possible candidates are:

btrev43089 hrev47741 hrev47742

[edglex]

I also have this problem on hrev47826 with an i5-3230M

[korli]

The reporter might confirm which flavor he is using, probably a GCC4 kernel based one.

[kim1963]

Replying to korli:

The reporter might confirm which flavor he is using, probably a GCC4 kernel based one.

hrev x86_gcc2 !!

​http://s015.radikal.ru/i332/1409/01/8c7fb6e60058.png

[korli]

Replying to kim1963:

Replying to korli:

The reporter might confirm which flavor he is using, probably a GCC4 kernel based one.

hrev x86_gcc2 !!

This is weird, I was under the impression that these commits only affects GCC4 builds.

[waddlesplash]

Assigning this to the A5 milestone makes sense to me, but I don't really agree that this should be a blocker. Does it prevent use of the computer in any way?

[pulkomandy]

It puts the hardware in danger of overheating. I wouldn't want to run a computer that way.

[edglex]

I am on gcc2 hybrid

[kim1963]

Update to hrev48031 x86_gcc2 -- no bug. Update to hrev48060 x86_gcc2 -- no bug. Update to hrev48068 x86_gcc2 -- no bug. Update to hrev48074 x86_gcc2 -- retry bug!!!

Possible candidates are: hrev48069 - hrev48074

[waddlesplash]

That doesn't make any sense. None of those commits affect the kernel except for hrev48074, and that only affects x86_64 not x86_gcc2. Even if they did, you said that hrev47748 had the problem. right? So did it just vanish between hrev47748 and hrev48031?

This is starting to sound like an intermittent failure to me, unless there's something else going on.

[kim1963]

So did it just vanish between hrev47748 and hrev48031?

Yes.

PS Changed 6 weeks ago by edglex

I also have this problem on hrev47826 with an i5-3230M

47826 - 48031 ?

[waddlesplash]

The only one of those commits that has anything to do with the kernel is hrev47830, and that changed display code, not CPU code. CPUIdle code has not been touched since the scheduler merge in January or so, IIRC.

Are you sure nothing else is changing? Maybe reboot a few times on one hrev and make sure it happens none of those times?

[kim1963]

​http://s49.radikal.ru/i125/1410/79/64b4fba0c33f.png

hrev48074 x86_gcc2 -- retry bug!!!

hrev48068 x86_gcc2 -- no bug.

[pulkomandy]

There wasn't any possibly related change in this commit range. So the problem must be somewhere else.

• Are you using the nightlies or compiling yourself? Maybe one of the buildbots generates different/broken images? (hrev48074 built by geist-bot3-ubuntu64 - hrev48068 built by zooey-bot2-suse)
• Does cold boot / reboot from haiku / reboot from another system makes any difference?

How to check which bot built which image:

• go to ​http://buildbot.haiku-os.org/builders/haiku-nightlies-x86_gcc2_hybrid and find matching build (in each build page, the build property "commit description" shows the hrev)
• look for slaveName in the build properties.

[kim1963]

Are you using the nightlies or compiling yourself? Maybe one of the buildbots generates different/broken images? (hrev48074 built by geist-bot3-ubuntu64 - hrev48068 built by zooey-bot2-suse)

---

[waddlesplash]

@kim1963, you realize that having "Idle Thread" use 100% CPU is *not* an indicator of the bug? The only indicator of the bug is your CPU getting very hot. So this screenshot doesn't demonstrate anything.

[pulkomandy]

Diver helped investigate this with kim.

The package bundled in the nightlies works fine. But the packages in the repo trigger the issue. You can see they are different on these screenshots: ​http://i.imgur.com/h70W6dP.png ​http://i.imgur.com/XQAZH2K.png

So it is some misconfiguration of arfonzo's bot (which builds most of the packages for the repos) or the repository buildbot recipe leading to a broken system. We still don't know exactly what's different in that case, however.

[kim1963]

pkgman update from hrev48074 - hrev48079 - no bug !

[kim1963]

Update to hrev48086 x86_gcc2 -- no bug!!! Update to hrev48100 x86_gcc2 -- retry bug!!! ​http://buildbot.haiku-os.org/buildslaves/arfonzo-bot1-debian

[Paradoxon]

Problem on hrev 48196

[kim1963]

hrev48196 ​http://buildbot.haiku-os.org/builders/haiku-repository-x86_gcc2_hybrid/builds/763

[kim1963]

Update to hrev48433 x86_gcc2 -- no bug Update to hrev48440 x86_gcc2 -- BUG !!! ​http://buildbot.haiku-os.org/builders/haiku-repository-x86_gcc2_hybrid/builds/987

[kim1963]

Update to hrev48444 -- bug! ​http://buildbot.haiku-os.org/builders/haiku-repository-x86_hybrid/builds/952

[kim1963]

Update to hrev48455 -- bug! Update to hrev48457 -- bug!

[kim1963]

4 Intel Core™ i3-3110M, revision 306a9 running at 2394MHz

CPU #0: "Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz"

Raw CPUID: 0x0306a9, Type 0, family 6, model 58, stepping 9, features 0xbfebfbff

FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CFLUSH DS ACPI MMX FXSTR SSE SSE2 SS HTT TM PBE

Extended Intel: 0x35bae3bf

SSE3 PCLMULDQ DTES64 MONITOR DS-CPL VMX EST TM2 SSSE3 CX16 xTPR PDCM PCID SSE4.1 SSE4.2 x2APIC POPCNT TSC-DEADLINE XSAVE AVX F16C

Extended AMD: type 0, family 0, model 0, stepping 0, features 0x28100000

NX RDTSCP 64

Power Management Features:

L2 Data cache fully associative, 1 lines/tag, 64 bytes/line L2 cache: 0 KB, 1-way set associative, 0 lines/tag, 63 bytes/line

Data TLB: 2M/4M-bytes pages, 4-way set associative, 32 entries Data TLB: 4k-byte pages, 4-way set associative, 64 entries Unknown cache descriptor 0x76 Unknown cache descriptor 0xff Inst TLB: 4K-bytes pages, 4-way set associative, 64 entries 64-byte Prefetching Shared 2nd-level TLB: 4K, 4-way set associative, 512 entries

hrev48818 - no bug hrev48845 hrev48881 - bug

[kim1963]

hrev49068 - no bug !!! ​http://buildbot.haiku-os.org/builders/haiku-repository-x86_gcc2_hybrid/builds/1560

[pulkomandy]

After hrev48973 the misbehaving buildbot was put offline: ​http://buildbot.haiku-os.org/buildslaves/arfonzo-bot1-debian

It uses a stable debian install, which has outdated libraries and cannot compile Haiku properly anymore. I am closing this ticket as I think any bot with more up to date software will not have this problem anymore. Please let us know if you hit the problem again.

It's also possible that hrev49058 helped fix this issue.

[kim1963]

Please let us know if you hit the problem again.

OK ​http://buildbot.haiku-os.org/buildslaves/luroh-bot1-xubuntu64 - no bug