kernel-packages team mailing list archive

[Launchpad Bug Tracker <1248492@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package linux - 3.12.0-3.8

---------------
linux (3.12.0-3.8) trusty; urgency=low

  [ Andy Whitcroft ]

  * [Config] armhf: PSTORE_RAM=y and PSTORE_CONSOLE=y
    - LP: #1248492

  [ Grygorii Strashko ]

  * SAUCE: ARM: OMAP4460: cpuidle: Extend
    PM_OMAP4_ROM_SMP_BOOT_ERRATUM_GICD on cpuidle

  [ John Johansen ]

  * SAUCE: (no-up) apparmor: Fix tasks not subject to, reloaded policy
    - LP: #1236455

  [ Paolo Pisati ]

  * [Config] disable ARM_HIGHBANK_CPUIDLE

  [ Tim Gardner ]

  * [Config] CONFIG_DEBUG_BUGVERBOSE=y
    - LP: #1252353
  * Release tracker
    - LP: #1252455
 -- Tim Gardner <tim.gardner@xxxxxxxxxxxxx>   Tue, 12 Nov 2013 07:28:53 -0700

** Changed in: linux (Ubuntu Trusty)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1248492

Title:
  [saucy] [armhf] use pstore to save console log messages

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Saucy:
  Fix Committed
Status in “linux” source package in Trusty:
  Fix Released

Bug description:
  SRU Justification:

  Impact: on platforms when there's a persistent memory storage (or when
  ram is not cleared during bootup like on arm), pstore and it's pstore-
  ram backend can be used to to save log messages on a previously
  defined and unallocated memory portion. Unfortunately, if we want to
  save bootup messages, we need the pstore-ram backend to be build in.

  Fix: apply the attached patch and recompile.

  Test: e.g., for a 256MB board, bootup a kernel with the following
  parameters:

  "mem=128M ramoops.mem_address=0x8000000 ramoops.mem_size=1048576"

  mem will tell the kernel to use only the first 128MB of ram, while ramoops address and size will the pstore where to find its storage and how big it is.
  Later on you can retrieve those messages from the u-boot command line dumping that memory region (mdw 0x8000000...) or you can bootup another kernel, mount pstore and retrieve the logs stored there:

  mount -t pstore  - /sys/fs/pstore
  cp /sys/fs/pstore/dmesg* .

  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248492/+subscriptions