Bug 875103
| Summary: | kswapd0 pegging a CPU with 3.7 kernel | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bruno Wolff III <bruno> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | bruno, gansalmon, itamar, john.ellson, jonathan, kernel-maint, madhu.chinakonda |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-11-12 13:59:39 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Bruno Wolff III
2012-11-09 14:40:57 UTC
I found this in my logs that might be related: Nov 9 23:21:41 bruno kernel: [ 1516.032006] BUG: soft lockup - CPU#0 stuck for 22s! [kswapd0:30] That was with 3.7.0-0.rc4.git0.1.fc19.i686.PAE. This morning I am trying 3.7.0-0.rc4.git2.2.fc19.i686.PAE and I am not seeing kswapd0 go wild yet running rpm. I'll test yum again in a bit. The system is an athlon mp with two processors. My file systems are ext4 on top of luks encrypted devices on top of software raid 1 devices. (/boot isn't encrypted.) Eventually I did see kswapd0 hit 90+% usage while running yum. I'm going to try using 3.6.6-4 for a bit and make sure I kswapd0 isn't doing that with 3.6 kernels. I am still seeing this with 3.7.0-0.rc4.git3.2.fc19.i686.PAE. I am not seeing as much slow down in the system (at least so far) as I did with some of the earlier kernels. It got to where yum updates ground to a halt. So there may have been some other problem that was really giving me grief. Though it still seems odd that kswapd0 goes cpu bound for an extended period when it doesn't look like there is significant swapping going on. I haven't noticed that happening with 3.6 kernels. This is probably a duplicate of 866988 *** This bug has been marked as a duplicate of bug 866988 *** |