tiomap-dev team mailing list archive

[Ming Lei <633227@xxxxxxxxxxxxxxxxxx>]

Seems A1 board is more stable than EA1 version.

I had one EA1 pandaboard before, but was destroyed, so I buy another A1
board.

Attach the kernel building log(build_log.tar.gz) and the config file(20110214-panda.log.tar.gz)
used in building kernel for my A1 pandaboard.

>From the log, you may see I can succeed in building kernel on Pandaboard for 2 times
and no any kernel error has been observed, both highmem and 3G/1G option are enabled 

In fact, I have tried doing the below also to reproduce the issue by building kernel on
Pandaboard A1, but did not succeed in triggering the issue on my board:
         - building kernel on SD card
         - use gcc-4.5.1
         - use same kernel parameters with Brywu
         - building kernel after consuming 512M memory by test code wrote by me

So does the issue only exist in old EA1 hardware? Maybe we may ask other guys
to try reproducing the issue on their A1 board to see if the same result can be got.


** Attachment added: "log.tar.gz"
   https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/633227/+attachment/1851164/+files/log.tar.gz

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

Title:
  instabilities with highmem activated

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

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.