linux-toradex.git/drivers/char/ramoops.c, branch v3.1.1

ramoops: update module parameters

2011-08-04T00:25:21+00:00

Update the module parameters when platform data is used.  This means
that they can be read from /sys/module/ramoops/parameters in order to
parse the memory area.

Signed-off-by: Sergiu Iordache 
Cc: Marco Stornelli 
Cc: Seiji Aguchi 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

ramoops: fix compile failure on parisc

2011-07-30T06:41:09+00:00

Fixes this:

  drivers/char/ramoops.c: In function 'ramoops_init':
  drivers/char/ramoops.c:221: error: implicit declaration of function 'IS_ERR'
  drivers/char/ramoops.c:222: error: implicit declaration of function 'PTR_ERR'

If it actually builds on other platforms, it's probably getting
linux/err.h via some other #include.

Signed-off-by: James Bottomley 
Signed-off-by: Linus Torvalds

ramoops: make record_size a module parameter

2011-07-26T23:49:46+00:00

The size of the dump is currently set using the RECORD_SIZE macro which
is set to a page size.  This patch makes the record size a module
parameter and allows it to be set through platform data as well to allow
larger dumps if needed.

Signed-off-by: Sergiu Iordache 
Acked-by: Marco Stornelli 
Cc: "Ahmed S. Darwish" 
Cc: Artem Bityutskiy 
Cc: Kyungmin Park 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

ramoops: move dump_oops into platform data

2011-07-26T23:49:45+00:00

The platform driver currently allows setting the mem_size and
mem_address.

ince dump_oops is also a module parameter it would be more consistent if
it could be set through platform data as well.

Signed-off-by: Sergiu Iordache 
Acked-by: Marco Stornelli 
Cc: "Ahmed S. Darwish" 
Cc: Artem Bityutskiy 
Cc: Kyungmin Park 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

ramoops: add new line to each print

2011-07-26T23:49:45+00:00

Add new line to each print.

Signed-off-by: Marco Stornelli 
Reported-by: Stevie Trujillo 
Cc: Kyungmin Park 
Cc: Américo Wang 
Cc: Joe Perches 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

ramoops: use module parameters instead of platform data if not available

2011-07-26T23:49:45+00:00

Use generic module parameters instead of platform data, if platform data
are not available.  This limitation has been introduced with commit
c3b92ce9e75 ("ramoops: use the platform data structure instead of module
params").

[akpm@linux-foundation.org: coding-style fixes]
Signed-off-by: Marco Stornelli 
Cc: Kyungmin Park 
Cc: Américo Wang 
Reported-by: Stevie Trujillo 
Cc: Joe Perches 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

ramoops: fix types, remove typecasts

2011-01-13T16:03:23+00:00

Cc: Ahmed S. Darwish 
Cc: Kyungmin Park 
Cc: Marco Stornelli 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

kmsg_dump: constrain mtdoops and ramoops to perform their actions only for KMSG_DUMP_PANIC

2011-01-13T16:03:07+00:00

This series aims to develop logging facility for enterprise use.

It is important to save kernel messages reliably on enterprise system
because they are helpful for diagnosing system.

This series add kmsg_dump() to the paths loosing kernel messages.  The use
case is the following.

[Use case of reboot/poweroff/halt/emergency_restart]

 My company has often experienced the followings in our support service.
 - Customer's system suddenly reboots.
 - Customers ask us to investigate the reason of the reboot.

We recognize the fact itself because boot messages remain in
/var/log/messages.  However, we can't investigate the reason why the
system rebooted, because the last messages don't remain.  And off course
we can't explain the reason.

We can solve above problem with this patch as follows.

 Case1: reboot with command
   - We can see "Restarting system with command:" or ""Restarting system.".

 Case2: halt with command
   - We can see "System halted.".

 Case3: poweroff with command
   - We can see " Power down.".

 Case4: emergency_restart with sysrq.
   - We can see "Sysrq:" outputted in __handle_sysrq().

 Case5: emergency_restart with softdog.
   - We can see "Initiating system reboot" in watchdog_fire().

So, we can distinguish the reason of reboot, poweroff, halt and emergency_restart.

If customer executed reboot command, you may think the customer should
know the fact.  However, they often claim they don't execute the command
when they rebooted system by mistake.

No message remains on the current Linux kernel, so we can't show the proof
to the customer.  This patch improves this situation.

This patch:

Alters mtdoops and ramoops to perform their actions only for
KMSG_DUMP_PANIC, KMSG_DUMP_OOPS and KMSG_DUMP_KEXEC because they would
like to log crashes only.

Signed-off-by: Seiji Aguchi 
Cc: David Woodhouse 
Cc: Marco Stornelli 
Reviewed-by: Artem Bityutskiy 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

RAMOOPS: Don't overflow over non-allocated regions

2010-12-28T19:12:32+00:00

The current code mis-calculates the ramoops header size, leading to an
overflow over the next record at best, or over a non-allocated region at
worst.  Fix that calculation.

Signed-off-by: Ahmed S. Darwish 
Acked-by: Marco Stornelli 
Cc: stable@kernel.org
Signed-off-by: Linus Torvalds

ramoops: use the platform data structure instead of module params

2010-10-28T01:03:18+00:00

As each board and system has different memory for ramoops.  It's better to
define the platform data instead of module params.

[akpm@linux-foundation.org: fix ramoops_remove() return type]
Signed-off-by: Kyungmin Park 
Cc: Marco Stornelli 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds