tiomap-dev team mailing list archive

[Oliver Grawert <ogra@xxxxxxxxxx>]

we still cant use the full 1G, while the patch improves it and 768M are
now usable with special bootoptions, i will reopen so we can track the
issue until it is completely fixed.

(the bootoptions we use in the current images: mem=460M@0x80000000
mem=256M@0xA0000000)

** Changed in: linux-ti-omap4 (Ubuntu)
       Status: Fix Released => Confirmed

** Changed in: linux-ti-omap4 (Ubuntu)
    Milestone: ubuntu-10.10 => ubuntu-11.04

-- 
instabilities with highmem activated
https://bugs.launchpad.net/bugs/633227
You received this bug notification because you are a member of TI OMAP
Developers, which is a direct subscriber.

Status in “linux-ti-omap4” package in Ubuntu: Confirmed
Status in “linux-ti-omap4” source package in Maverick: Fix Released

Bug description:
Seen on Maverick: 2.6.35-903.9
HW: pandaboard ES2.0

Using following kernel memory allocation (in bootargs):
mem=460M@0x80000000 mem=512M@0xA0000000

Instabilities have been observed in 2 different ways:

1) The following memtester test:
sudo memtester -p 0xb0000000 120
Fails in few seconds with a "illegal instruction” error.
Then various behaviors can be seen:  the UI can freeze, shell commands be unavailable. The systems works well again after a reboot.

2) By doing a native build of a kernel package (with file-system on SD card, and kernel sources on an NFS mount):
After 15mins to 1h30, a "compiler error: bus error" triggers and the build stops (and the platform hangs).


This issue cannot be reproduced if using mem=460M@0x80000000 mem=256M@0xA000000.
This issue cannot be reproduced with highmen deactivated from the kernel config.
This issue can be reproduced with 'nosmp' in kernel command line.