Re: [PATCH 1/2] kdump: Allow shrinking of kdump region to be overridden

2011-03-15 Thread Américo Wang
On Tue, Mar 15, 2011 at 2:13 AM, Mahesh J Salgaonkar wrote: > > During free we do free all of them including RMO region. But since the rtas > region is always on top of RMO, crashkernel memory overlaps rtas region and > we endup freeing that even, which is causing the crash. > Okay, but with this

Re: [PATCH 1/2] kdump: Allow shrinking of kdump region to be overridden

2011-03-09 Thread Américo Wang
On Wed, Mar 09, 2011 at 11:46:57PM +1100, Anton Blanchard wrote: > >Hi, > >> The crashkernel region is specified via kernel cmdline, so why >> not just drop a failure when it overlaps with RMO region? >> Am I missing something? > >Unfortunately a ppc64 kernel requires a chunk of RMO memory. We woul

Re: [PATCH 1/2] kdump: Allow shrinking of kdump region to be overridden

2011-03-09 Thread Américo Wang
On Wed, Mar 09, 2011 at 12:02:06PM +0530, Mahesh Jagannath Salgaonkar wrote: >On 08/25/2010 06:07 AM, Eric W. Biederman wrote: >> Anton Blanchard writes: >> >>> On ppc64 the crashkernel region almost always overlaps an area of firmware. >>> This works fine except when using the sysfs interface to

Re: [PATCH] powerpc: Add vmcoreinfo symbols to allow makdumpfile to filter core files properly

2010-07-27 Thread Américo Wang
On Mon, Jul 26, 2010 at 11:23 PM, Neil Horman wrote: > On Tue, Jul 13, 2010 at 09:46:09AM -0400, Neil Horman wrote: >> Hey all- >>       About 2 years ago now, I sent this patch upstream to allow makedumpfile >> to properly filter cores on ppc64: >> http://www.mail-archive.com/ke...@lists.infradea

Re: [PATCH] Restrict stack space reservation to rlimit

2010-02-07 Thread Américo Wang
On Mon, Feb 8, 2010 at 2:05 PM, KOSAKI Motohiro wrote: >> --- linux-2.6-ozlabs.orig/fs/exec.c >> +++ linux-2.6-ozlabs/fs/exec.c >> @@ -627,10 +627,13 @@ int setup_arg_pages(struct linux_binprm >>                       goto out_unlock; >>       } >> >> +     stack_base = min(EXTRA_STACK_VM_PAGES *

Re: 2.6.32 Kernel panic - not syncing: Attempted to kill init! Rebooting in 180 seconds..

2009-12-17 Thread Américo Wang
On Fri, Dec 18, 2009 at 3:38 PM, Zhiyong Wu wrote > On Fri, Dec 18, 2009 at 3:12 PM, Américo Wang > wrote: >> On Fri, Dec 18, 2009 at 12:08 PM, Zhiyong Wu wrote: >>> HI, >>> >>> linux-2.6.32 is compiled on a p6 machine with RH5.4 OS and KVM option is

Re: 2.6.32 Kernel panic - not syncing: Attempted to kill init! Rebooting in 180 seconds..

2009-12-17 Thread Américo Wang
On Fri, Dec 18, 2009 at 12:08 PM, Zhiyong Wu wrote: > HI, > > linux-2.6.32 is compiled on a p6 machine with RH5.4 OS and KVM option is > enable. > > When rebooting this machine, a crash takes place such as: > > Loading ramdisk... > ramdisk loaded at 0170, size: 2700 Kbytes > OF stdout device

Re: [PATCH] BUILD_BUG_ON: make it handle more cases

2009-10-22 Thread Américo Wang
On Tue, Oct 20, 2009 at 10:43 PM, Alan Jenkins wrote: > On 10/20/09, Américo Wang wrote: >> On Tue, Oct 20, 2009 at 02:15:33PM +1030, Rusty Russell wrote: >>>BUILD_BUG_ON used to use the optimizer to do code elimination or fail >>>at link time; it was changed to f

Re: [PATCH] BUILD_BUG_ON: make it handle more cases

2009-10-20 Thread Américo Wang
On Tue, Oct 20, 2009 at 02:15:33PM +1030, Rusty Russell wrote: >BUILD_BUG_ON used to use the optimizer to do code elimination or fail >at link time; it was changed to first the size of a negative array (a >nicer compile time error), then (in >8c87df457cb58fe75b9b893007917cf8095660a0) to a bitfield.