[regression] since linux 3.4.0, kswapd0 uses 100% cpu when low memory is available
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
When the system runs with low available memory, kswapd0 starts running consuming 100% of one cpu and persisting in this state until I close some processes to free up a large amount of memory.
I can easily reproduce this problem, as it happens every time the system memory goes up to about 80%, but it's not limited to this case.
The regression was introduced in version 3.4.0 (downloaded directly from kernel.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-
ProcVersionSign
Uname: Linux 3.5.0-15-generic i686
NonfreeKernelMo
ApportVersion: 2.5.2-0ubuntu4
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory: 'iw'
CurrentDmesg:
[ 47.206985] NVRM: Your system is not currently configured to drive a VGA console
[ 47.206994] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[ 47.207001] NVRM: requires the use of a text-mode VGA console. Use of other console
[ 47.207007] NVRM: drivers including, but not limited to, vesafb, may result in
[ 47.207013] NVRM: corruption and stability problems, and is not supported.
Date: Mon Sep 24 16:29:42 2012
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120910)
MachineType: SAMSUNG ELECTRONICS CO., LTD. N510
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 1.93
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/24/2009
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 02MU.M004.
dmi.board.name: N510
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: N510
dmi.product.
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
I'd like to perform a bisect to figure out what commit caused this regression. It would be very helpful to know the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue.
Can you test the following kernels and report back? We are looking for the first kernel version that doesn't have this bug:
v3.4-rc1: http:// kernel. ubuntu. com/~kernel- ppa/mainline/ v3.4-rc1- precise/ kernel. ubuntu. com/~kernel- ppa/mainline/ v3.4-rc2- precise/ kernel. ubuntu. com/~kernel- ppa/mainline/ v3.4-rc3- precise/
v3.4-rc2: http://
v3.4-rc3: http://
...
You don't have to test every kernel, just up until the kernel that first has this bug.
Thanks in advance!