High load averages on Lucid while idling

Bug #683013 reported by Peter Júnoš
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
Lucid
Invalid
Undecided
Unassigned

Bug Description

There are 2 HDDs in SW raid1, ext3, deadline scheduler and much higher loads and CPU usage after upgrade to Lucid. Cpu: http://bayimg.com/JAAdOaaDo Fork rate: http://bayimg.com/IaadkaADo Interrupts: http://bayimg.com/iaaDLAAdo IRQ stats http://bayimg.com/IAAdmaadO Load http://bayimg.com/iaAdnaaDO Individual Interrupts http://bayimg.com/iaADOaado VMStat http://bayimg.com/KAADbAADo

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-25-server 2.6.32-25.45
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-25.45-server 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-server x86_64
NonfreeKernelModules: ksplice_2j0nhczs ksplice_wsezy5qm ksplice_kbveoa2w ksplice_0hanf5d6 ksplice_2c43k68c ksplice_mqoghill ksplice_2m2ow24r ksplice_cmm72wdd_vmlinux_new ksplice_cmm72wdd ksplice_f8zlckse_vmlinux_new ksplice_f8zlckse ksplice_d0fz3e13_vmlinux_new ksplice_d0fz3e13
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
Date: Tue Nov 30 09:37:59 2010
HibernationDevice: RESUME=UUID=deda08e1-8a7c-4b5c-ae87-238498c29d95
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 002 Device 002: ID 8087:0020
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 04d9:1400 Holtek Semiconductor, Inc.
 Bus 001 Device 002: ID 8087:0020
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-25-server root=UUID=ec0a3dab-85e2-4898-aa47-e7f9e36a057f ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.1
RfKill:

SourcePackage: linux
WifiSyslog:
 Nov 30 06:52:52 server kernel: [492809.162010] hlds_i686[29851]: segfault at a0a140 ip 00000000f76a0fd0 sp 00000000ffe0d9b0 error 4 in libc-2.11.1.so[f7641000+153000]
 Nov 30 07:41:42 server kernel: [495739.830680] hlds_i686[29742]: segfault at 0 ip 00000000f4bec5bb sp 00000000ffa41b90 error 4 in amxmodx_mm_i386.so[f4bc5000+6f000]
 Nov 30 07:41:53 server kernel: [495750.980815] hlds_i686[2932]: segfault at 9980f8 ip 00000000f766cfd0 sp 00000000ffe79230 error 4 in libc-2.11.1.so[f760d000+153000]
 Nov 30 07:42:04 server kernel: [495761.087708] hlds_i686[2940]: segfault at 90f8 ip 00000000f766afd0 sp 00000000ffd97350 error 4 in libc-2.11.1.so[f760b000+153000]
 Nov 30 07:42:14 server kernel: [495771.188378] hlds_i686[2948]: segfault at 7990f8 ip 00000000f75fcfd0 sp 00000000ffa67ba0 error 4 in libc-2.11.1.so[f759d000+153000]
dmi.bios.date: 08/02/2009
dmi.bios.vendor: Intel Corp.
dmi.bios.version: WBIBX10J.86A.0122.2009.0802.2219
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DP55WB
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE64798-204
dmi.chassis.type: 2
dmi.modalias: dmi:bvnIntelCorp.:bvrWBIBX10J.86A.0122.2009.0802.2219:bd08/02/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55WB:rvrAAE64798-204:cvn:ct2:cvr:

Revision history for this message
Peter Júnoš (petoju) wrote :
Revision history for this message
Peter Júnoš (petoju) wrote :

ec2 version is probably already fixed - is it so hard to port fix to server version?

Revision history for this message
Peter Júnoš (petoju) wrote :

Subscribing Scott Moser as he requested bug report with ubuntu-bug.

Revision history for this message
Scott Moser (smoser) wrote :

The EC2 bug that was fixed as accounting only.
If you're seeing *real* performance regression, than that simple fix (which was xen specific, I believe) will not help.

Revision history for this message
Peter Júnoš (petoju) wrote :

Yes, I see real performance regressions (lags on game servers), so something like only returning 0.1x this value won't fix it.

Revision history for this message
Jesse Newland (jnewland) wrote :

I'm seeing real performance regressions *and* accounting issues when running the -server kernel on xen outside of ec2. I'm happy to help in any way possible to help debug this.

Revision history for this message
Jesse Newland (jnewland) wrote :

Created #690848 as a dupe of this to attach one affected box's debug info. I'm seeing this on multiple lucid domUs.

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
DLHDavidLH (dlhdavidlh-yahoo) wrote :

High load average on Ubuntu 10.04 ...( 64 bit )

- Ubuntu 10.04 (64bit)
- Linux kernel 2.6.32-30
- Gnome 2.30.2

---------------------------------------------------------------------------------

- - computer specs - -

* AMD Phenom II X6 1055T ( 2.8GHz )

* ECS A790GXM-AD3 ( AMD 790GX North bridge / SB750 south bridge )

* 6 GB of DD3 1333 Memory

* WD3000HLFS ( SATA and 10000 RPM ) 300GB Hard drive

Revision history for this message
DLHDavidLH (dlhdavidlh-yahoo) wrote :

it also affects . . .

High load averages on Ubuntu 10.10
( Maverick Meerkat )-( 64 bit version )-( Live CD )

* while idling *

-------------------------------

- Ubuntu 10.10 ( 64bit )
- Linux kernel 2.6.35-22
- Gnome 2.30.0

---------------------------------------------------------------------------------

- - computer specs - -

* AMD Phenom II X6 1055T ( 2.8GHz )

* ECS A790GXM-AD3 ( AMD 790GX North bridge / SB750 south bridge )

* 6 GB of DD3 1333 Memory

* WD3000HLFS ( SATA and 10000 RPM ) 300GB Hard drive

Revision history for this message
penalvch (penalvch) wrote :

Peter Júnoš, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

summary: - High load averages on Lucid while idling [#574910 via ubuntu-bug]
+ High load averages on Lucid while idling
tags: added: bios-outdated-0336
description: updated
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Peter Júnoš (petoju) wrote :

Sorry, I cannot test it as the machine with Lucid is gone (personally, I use much newer Raring now and problem seems to be fixed there, but I cannot really compare it).

Revision history for this message
penalvch (penalvch) wrote :

Peter Júnoš, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/683013/comments/11 regarding you no longer have the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Changed in linux (Ubuntu Lucid):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.