Public bug reported:
Binary package hint: linux-image-2.6.20-16-generic
Sometimes (not particular reprodusable) we have jobs like the one on the
screenshot allocated on our compute cluster. This jobs is not utillizing
the CPU's as it should. 2 individual processes on a 2-CPU machine leaves
1 x 100% cpu and about 50% idle CPU.
The cluster is Ubuntu Feisty 7.04 machines with:
[EMAIL PROTECTED]:~$ uname -a
Linux node04 2.6.20-16-generic #2 SMP Sun Sep 23 18:31:23 UTC 2007 x86_64
GNU/Linux
[EMAIL PROTECTED]:~$
[EMAIL PROTECTED]:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 7.04
Release: 7.04
Codename: feisty
[EMAIL PROTECTED]:~$ uname -a
Linux node04 2.6.20-16-generic #2 SMP Sun Sep 23 18:31:23 UTC 2007 x86_64
GNU/Linux
[EMAIL PROTECTED]:~$ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 5
model name : AMD Opteron(tm) Processor 244
stepping : 10
cpu MHz : 1794.886
cache size : 1024 KB
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow
bogomips : 3595.24
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp
processor : 1
vendor_id : AuthenticAMD
cpu family : 15
model : 5
model name : AMD Opteron(tm) Processor 244
stepping : 10
cpu MHz : 1794.886
cache size : 1024 KB
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow
bogomips : 3589.83
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp
** Affects: linux-source-2.6.20 (Ubuntu)
Importance: Undecided
Status: New
--
Program not utillizing the CPU fully
https://bugs.launchpad.net/bugs/185987
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
