Re: kdump broken on Altix 350

2008-10-01 Thread Simon Horman
On Mon, Sep 29, 2008 at 04:42:52PM -0700, Luck, Tony wrote: Does this make kexec/kdump happier? Bare minimum testing so far (builds and boots on tiger ... didn't try kexec yet). Hi Tony, your analysis (in your previous email) was more or less the same conclusion that I had come too, though I

RE: kdump broken on Altix 350

2008-09-29 Thread Luck, Tony
Maybe I'm starting to see what happened ... and it could well be my fault. I wanted to allocate the per-cpu memory for cpu0 statically in the vmlinux ... so it would be available in head.S to set up everything before we move to any C code that might try to access per cpu variables. To make life

RE: kdump broken on Altix 350

2008-09-29 Thread Luck, Tony
Does this make kexec/kdump happier? Bare minimum testing so far (builds and boots on tiger ... didn't try kexec yet). [IA64] Put the space for cpu0 per-cpu area into .data section Initial fix for making sure that we can access percpu variables in all C code commit:

Re: kdump broken on Altix 350

2008-09-29 Thread Jay Lan
Luck, Tony wrote: Does this make kexec/kdump happier? Bare minimum testing so far (builds and boots on tiger ... didn't try kexec yet). Hi Tony, Yep, the 2.6.27-rc7 kdump kernel built with this patch worked fine! Actually you probably can predict the results by doing 'readelf -l vmlinux'. If

Re: kdump broken on Altix 350

2008-09-26 Thread Jay Lan
Jay Lan wrote: Bernhard Walle wrote: * Luck, Tony [EMAIL PROTECTED] [2008-08-29]: your commit commit 10617bbe84628eb18ab5f723d3ba35005adde143 Author: Tony Luck [EMAIL PROTECTED] Date: Tue Aug 12 10:34:20 2008 -0700 [IA64] Ensure cpu0 can access per-cpu variables in

Re: kdump broken on Altix 350

2008-09-10 Thread Bernhard Walle
* Luck, Tony [EMAIL PROTECTED] [2008-08-29]: your commit commit 10617bbe84628eb18ab5f723d3ba35005adde143 Author: Tony Luck [EMAIL PROTECTED] Date: Tue Aug 12 10:34:20 2008 -0700 [IA64] Ensure cpu0 can access per-cpu variables in early boot code broke kdump

Re: kdump broken on Altix 350

2008-09-10 Thread Bernhard Walle
* Bernhard Walle [EMAIL PROTECTED] [2008-08-29]: broke kdump on our Altix 350. I get following early crash in kdump kernel: Just as side note: I still have the problem with 2.6.27-rc6. Bernhard ___ kexec mailing list kexec@lists.infradead.org

Re: kdump broken on Altix 350

2008-09-10 Thread Jay Lan
Bernhard Walle wrote: * Luck, Tony [EMAIL PROTECTED] [2008-08-29]: your commit commit 10617bbe84628eb18ab5f723d3ba35005adde143 Author: Tony Luck [EMAIL PROTECTED] Date: Tue Aug 12 10:34:20 2008 -0700 [IA64] Ensure cpu0 can access per-cpu variables in early boot code

RE: kdump broken on Altix 350

2008-08-29 Thread Luck, Tony
your commit commit 10617bbe84628eb18ab5f723d3ba35005adde143 Author: Tony Luck [EMAIL PROTECTED] Date: Tue Aug 12 10:34:20 2008 -0700 [IA64] Ensure cpu0 can access per-cpu variables in early boot code broke kdump on our Altix 350. I get following early crash in kdump

RE: kdump broken on Altix 350

2008-08-29 Thread Bernhard Walle
Am Fr 29 Aug 2008 22:42:40 CEST schrieb Luck, Tony [EMAIL PROTECTED]: your commit commit 10617bbe84628eb18ab5f723d3ba35005adde143 Author: Tony Luck [EMAIL PROTECTED] Date: Tue Aug 12 10:34:20 2008 -0700 [IA64] Ensure cpu0 can access per-cpu variables in early boot code