Ralph, 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.
** Tags removed: 10.04 cpu high ksoftirqd
** Tags added: lucid needs-kernel-logs needs-upstream-testing
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Description changed:
On an HP DL380G6 running a fresh install of 10.04 LTS Server 64-bit, I
observed ksoftirqd hitting the CPU (up to 100%). Fortunately it limited
itself to one core. I did not see this on 9.10 Server 64-bit on the
same hardware. I installed the mainline kernel from today
(2.6.34-999-generic) and the problem did correct itself.
- I am attaching output from 'apport-bug -p linux' with the stock kernel
- and bug present; obviously I cannot do the same for the mainline kernel,
- but please let me know if there is any other information I can gather to
- help determine what is different.
-
- Per the request near the end of the responses in Bug #183461, I am
- filing a new bug report for this issue.
+ WORKAROUND: 1. Edit /boot/config-{kernversion}-server (on mine right now this
is 2.6.31-22); comment out any line with IPMI in it.
+ 2. Get rid of /lib/modules/2.6.31-22-server/kernel/drivers/char/ipmi/ipmi_*
(or whatever your kern version is). I moved these files to another location
just in case I needed them.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/575392
Title:
ksoftirqd high CPU on 10.04-LTS Server
Status in “linux” package in Ubuntu:
Incomplete
Status in “linux” package in CentOS:
Fix Released
Bug description:
On an HP DL380G6 running a fresh install of 10.04 LTS Server 64-bit, I
observed ksoftirqd hitting the CPU (up to 100%). Fortunately it
limited itself to one core. I did not see this on 9.10 Server 64-bit
on the same hardware. I installed the mainline kernel from today
(2.6.34-999-generic) and the problem did correct itself.
WORKAROUND: 1. Edit /boot/config-{kernversion}-server (on mine right now this
is 2.6.31-22); comment out any line with IPMI in it.
2. Get rid of /lib/modules/2.6.31-22-server/kernel/drivers/char/ipmi/ipmi_*
(or whatever your kern version is). I moved these files to another location
just in case I needed them.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/575392/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
