tiomap-dev team mailing list archive

[Launchpad Bug Tracker <633227@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.13

---------------
linux-ti-omap4 (2.6.35-903.13) maverick; urgency=low

  [ Bryan Wu ]

  * SAUCE: Fix a buidling error when turn off CONFIG_SMP
    - LP: #647890
  * [Config] Enable CONFIG_VMSPLIT_2G=y for OMAP4
    - LP: #633227

  [ Ricardo Salveti de Araujo ]

  * [Config] OMAP: Enable needed Errata for OMAP4 to work with DMA based
    device drivers

  [ Upstream Kernel Changes ]

  * ARM: do not define VMALLOC_END relative to PAGE_OFFSET
 -- Tim Gardner <tim.gardner@xxxxxxxxxxxxx>   Thu, 30 Sep 2010 17:04:40 +0100

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

-- 
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: Fix Released
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.