05-02-2013 09:19 PM
When I installed GPIB driver and run gpibexplorer, it said:
linux-qgcl:/usr/local/natinst/ni4882/bin # ./gpibexplorer
./source/lib/IntelDataCollector.cpp(2332): CPUID(2) returned unrecognized cacheID of 76.
./source/lib/IntelDataCollector.cpp(2323): Abandoning cache enumeration from CPUID(2). Using CPUID(4) instead.
./source/lib/IntelDataCollector.cpp(1013): Intel: CPUID(4) cache results did not all merge with CPUID(2).
./source/lib/IntelDataCollector.cpp(1105): Inconsistent L2 cache information. Searched for:
./source/lib/IntelDataCollector.cpp(1108): level: 2, role: 2; type: 0, entryType: 2, entrySize: 64, size: 262144, associativity: 8
./source/lib/IntelDataCollector.cpp(1110): Raw data was: eax: 00000000, ebx: 00000000, ecx: 01006040, edx: 00000000
./source/lib/IntelDataCollector.cpp(1111): L2 cache data from CPUID(2), CPUID(4) and CPUID(0x80000006) report a mismatch.
./source/lib/IntelDataCollector.cpp(976): CPUID(4) provided cache that CPUID(2) did not. Intel cache parse may need an update.
./source/lib/IntelDataCollector.cpp(976): CPUID(4) provided cache that CPUID(2) did not. Intel cache parse may need an update.
./source/lib/IntelDataCollector.cpp(976): CPUID(4) provided cache that CPUID(2) did not. Intel cache parse may need an update.
./source/lib/IntelDataCollector.cpp(976): CPUID(4) provided cache that CPUID(2) did not. Intel cache parse may need an update.
./source/lib/IntelDataCollector.cpp(2332): CPUID(2) returned unrecognized cacheID of 76.
./source/lib/IntelDataCollector.cpp(2323): Abandoning cache enumeration from CPUID(2). Using CPUID(4) instead.
./source/lib/IntelDataCollector.cpp(1013): Intel: CPUID(4) cache results did not all merge with CPUID(2).
./source/lib/IntelDataCollector.cpp(1105): Inconsistent L2 cache information. Searched for:
./source/lib/IntelDataCollector.cpp(1108): level: 2, role: 2; type: 0, entryType: 2, entrySize: 64, size: 262144, associativity: 8
./source/lib/IntelDataCollector.cpp(1110): Raw data was: eax: 00000000, ebx: 00000000, ecx: 01006040, edx: 00000000
./source/lib/IntelDataCollector.cpp(1111): L2 cache data from CPUID(2), CPUID(4) and CPUID(0x80000006) report a mismatch.
./source/lib/IntelDataCollector.cpp(976): CPUID(4) provided cache that CPUID(2) did not. Intel cache parse may need an update.
./source/lib/IntelDataCollector.cpp(976): CPUID(4) provided cache that CPUID(2) did not. Intel cache parse may need an update.
./source/lib/IntelDataCollector.cpp(976): CPUID(4) provided cache that CPUID(2) did not. Intel cache parse may need an update.
./source/lib/IntelDataCollector.cpp(976): CPUID(4) provided cache that CPUID(2) did not. Intel cache parse may need an update.
./source/lib/IntelDataCollector.cpp(2332): CPUID(2) returned unrecognized cacheID of 76.
./source/lib/IntelDataCollector.cpp(2323): Abandoning cache enumeration from CPUID(2). Using CPUID(4) instead.
./source/lib/IntelDataCollector.cpp(1013): Intel: CPUID(4) cache results did not all merge with CPUID(2).
./source/lib/IntelDataCollector.cpp(1105): Inconsistent L2 cache information. Searched for:
./source/lib/IntelDataCollector.cpp(1108): level: 2, role: 2; type: 0, entryType: 2, entrySize: 64, size: 262144, associativity: 8
./source/lib/IntelDataCollector.cpp(1110): Raw data was: eax: 00000000, ebx: 00000000, ecx: 01006040, edx: 00000000
./source/lib/IntelDataCollector.cpp(1111): L2 cache data from CPUID(2), CPUID(4) and CPUID(0x80000006) report a mismatch.
./source/lib/IntelDataCollector.cpp(976): CPUID(4) provided cache that CPUID(2) did not. Intel cache parse may need an update.
./source/lib/IntelDataCollector.cpp(976): CPUID(4) provided cache that CPUID(2) did not. Intel cache parse may need an update.
./source/lib/IntelDataCollector.cpp(976): CPUID(4) provided cache that CPUID(2) did not. Intel cache parse may need an update.
./source/lib/IntelDataCollector.cpp(976): CPUID(4) provided cache that CPUID(2) did not. Intel cache parse may need an update.
./source/lib/IntelDataCollector.cpp(2332): CPUID(2) returned unrecognized cacheID of 76.
./source/lib/IntelDataCollector.cpp(2323): Abandoning cache enumeration from CPUID(2). Using CPUID(4) instead.
./source/lib/IntelDataCollector.cpp(1013): Intel: CPUID(4) cache results did not all merge with CPUID(2).
./source/lib/IntelDataCollector.cpp(1105): Inconsistent L2 cache information. Searched for:
./source/lib/IntelDataCollector.cpp(1108): level: 2, role: 2; type: 0, entryType: 2, entrySize: 64, size: 262144, associativity: 8
./source/lib/IntelDataCollector.cpp(1110): Raw data was: eax: 00000000, ebx: 00000000, ecx: 01006040, edx: 00000000
./source/lib/IntelDataCollector.cpp(1111): L2 cache data from CPUID(2), CPUID(4) and CPUID(0x80000006) report a mismatch.
./source/lib/IntelDataCollector.cpp(976): CPUID(4) provided cache that CPUID(2) did not. Intel cache parse may need an update.
./source/lib/IntelDataCollector.cpp(976): CPUID(4) provided cache that CPUID(2) did not. Intel cache parse may need an update.
./source/lib/IntelDataCollector.cpp(976): CPUID(4) provided cache that CPUID(2) did not. Intel cache parse may need an update.
./source/lib/IntelDataCollector.cpp(976): CPUID(4) provided cache that CPUID(2) did not. Intel cache parse may need an update.
libnipalu.so failed to initialize
Perhaps you need to run updateNIDrivers
Aborted
Any body know why this happen?
My computer:
CPU Information
Processor (CPU): Intel(R) Core(TM) i3-2130 CPU @ 3.40GHz
Speed: 3,400.00 MHz
Cores: 4
Memory Information
Total memory (RAM): 3.8 GiB
Free memory: 2.5 GiB (+ 831.0 MiB Caches)
Free swap: 2.0 GiB
05-03-2013 09:13 AM
CPUID thing apparently is a known issue for lv runtime 2009. The fix I found looking in internal site in NI:
"the customer will need to manually copy the LabVIEW 2011 SP1 RTE version of the niCPULib.so file to the equivalent location for the LabVIEW 2009 RTE."
The killer one for you is the output of "libnipalu.so failed to initialize"
There are many threads on why this is the case if you search around the forum.
One I could think of, you seem to have 4 GB memory in the system : https://decibel.ni.com/content/message/23823
05-06-2013 12:47 AM
Thanks! I think it is the computer issure. I changed a 2 core cpu computer, then this problem was solved.
07-25-2018 09:27 AM
I really wonder why userland code ever has to cope w/ cache control.
(which shouldn't be accessible to unprivileged code, anyways)