Page allocation failure on Pandaboard and Beagle XM
Bug #746137 reported by
Tobin Davis
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jasper-initramfs (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Natty |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Unassigned | ||
Quantal |
Invalid
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
Natty |
Invalid
|
Undecided
|
Unassigned | ||
Precise |
Invalid
|
Undecided
|
Unassigned | ||
Quantal |
Invalid
|
High
|
Unassigned | ||
linux-ti-omap4 (Ubuntu) |
Fix Released
|
High
|
Paolo Pisati | ||
Natty |
Won't Fix
|
High
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Paolo Pisati | ||
Quantal |
Fix Released
|
High
|
Paolo Pisati |
Bug Description
During the course of testing, I have been seeing a lot of page allocation failures on all omap4 images. Not sure what the cause is, but it doesn't appear to be related to any specific application. This also doesn't appear to affect the execution of the application.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-
ProcVersionSign
Uname: Linux 2.6.38-1207-omap4 armv7l
Architecture: armel
Date: Wed Mar 30 16:59:55 2011
ProcEnviron:
LANGUAGE=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-ti-omap4
UpgradeStatus: No upgrade log present (probably fresh install)
Related branches
lp:~rsalveti/jasper-initramfs/746137
- Oliver Grawert (community): Approve
-
Diff: 45 lines (+22/-0)3 files modifieddebian/changelog (+7/-0)
scripts/local-bottom/jasper_setup (+3/-0)
sysctl/30-jasper-smsc-min-free-kbytes.conf (+12/-0)
tags: | added: iso-testing |
Changed in linux-ti-omap4 (Ubuntu): | |
importance: | Undecided → High |
summary: |
- Page allocation failure on omap4 + Page allocation failure on Pandaboard and Beagle XM |
Changed in linux-ti-omap4 (Ubuntu Quantal): | |
milestone: | none → ubuntu-12.10-beta-1 |
Changed in linux (Ubuntu Quantal): | |
milestone: | none → ubuntu-12.10-beta-1 |
tags: | added: rls-q-incoming |
Changed in linux-ti-omap4 (Ubuntu Quantal): | |
status: | New → Incomplete |
Changed in linux-ti-omap4 (Ubuntu Quantal): | |
status: | Incomplete → Confirmed |
Changed in jasper-initramfs (Ubuntu Quantal): | |
status: | Fix Released → Invalid |
Changed in linux (Ubuntu Quantal): | |
status: | Incomplete → Confirmed |
milestone: | ubuntu-12.10-beta-1 → ubuntu-12.10-beta-2 |
Changed in linux-ti-omap4 (Ubuntu Quantal): | |
milestone: | ubuntu-12.10-beta-1 → ubuntu-12.10-beta-2 |
Changed in jasper-initramfs (Ubuntu Precise): | |
status: | Fix Released → Invalid |
status: | Invalid → Fix Released |
Changed in linux-ti-omap4 (Ubuntu Quantal): | |
assignee: | nobody → Paolo Pisati (p-pisati) |
Changed in linux-ti-omap4 (Ubuntu Precise): | |
assignee: | nobody → Paolo Pisati (p-pisati) |
To post a comment you must log in.
Can you check if this still happens after adding "vm.min_free_kbytes = 8192" to your /etc/sysctl.conf?
From the logs it seems that the usb hub is trying to allocate big chucks of memory. That could be explained by using the rootfs on a usb disk or transferring a lot of data over ethernet.