kernel-packages team mailing list archive

[Brad Figg <brad.figg@xxxxxxxxxxxxx>]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1248492

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

** Tags added: saucy

-- 
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:
  Incomplete

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