[Fastboot] gdb does not analyse vmcore from kexec on 2.6.20

Hi, Thanks for your kexec/kdump tools. I was running linux-2.6.20 on x86_64 & my machine's RAM is > 4GB. Got the vmcore file (after following the steps in Documentation/kdump/kdump.txt). To analyse the core file, I am using gdb (version-6.4). Issues that I am facing with this: 1)"bt" gives

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

On 3/16/07, Horms <[EMAIL PROTECTED]> wrote: > On Fri, Mar 16, 2007 at 08:52:30AM +0530, Vivek Goyal wrote: > > So it will now be left to the user. If he tries to kexec to a 64bit kernel > > on a machine not supporting 32bit extensions, then kexec will not give > > any advance warning. > > I feel c

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

On Fri, Mar 16, 2007 at 08:52:30AM +0530, Vivek Goyal wrote: > On Fri, Mar 16, 2007 at 11:40:07AM +0900, Magnus Damm wrote: > > On 3/16/07, Horms <[EMAIL PROTECTED]> wrote: > > >On Thu, Mar 15, 2007 at 06:56:16PM +0530, Vivek Goyal wrote: > > >> On Thu, Mar 15, 2007 at 12:22:57PM +, Ian Campbel

[Fastboot] oversexed yrfr Cutie pql Gets Topless!

yoqxcf, lubricious ium Ladies hhgz playing with Toy!! http://thenevadaagent.info cqgkc lrgic iwmbmc cou. ___ fastboot mailing list fastboot@lists.osdl.org https://lists.osdl.org/mailman/listinfo/fastboot

[Fastboot] [PATCH] kexec: make mptsas_ioc_reset() fail cleanly if ioc->sh is NULL

In the interest of not dropping the ball, I have made a patch, as per the changes described by Eric, and tested by Judith. It may be wildly inaccurate. Please Review -- Horms H: http://www.vergenet.net/~horms/ W: http://www.valinux.co.jp/en/ Currently modprobe of mptsas fails after kexec.

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

On Fri, Mar 16, 2007 at 07:17:43AM +, Ian Campbell wrote: > On Fri, 2007-03-16 at 08:48 +0900, Horms wrote: > > > > > > > > Signed-off-by: Ian Campbell <[EMAIL PROTECTED]> > > > > > > > > diff --git a/fs/proc/vmcore.c b/fs/proc/vmcore.c > > > > index d960507..523e109 100644 > > > > --- a/fs/p

Re: [Fastboot] [PATCH] kexec-tools: arch_options seems to be unused on sh

On Fri, Mar 16, 2007 at 11:59:29AM +0900, Paul Mundt wrote: > On Fri, Mar 16, 2007 at 11:29:36AM +0900, Horms wrote: > > arch_options, declared in kexec/arch/sh/kexec-sh.c seems to be unused, > > so remove it. > > > Indeed. > > > Signed-off-by: Simon Horman <[EMAIL PROTECTED]> > > > Acked-by: Pa

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

On Fri, 2007-03-16 at 08:12 +0530, Vivek Goyal wrote: > I did not investigate deeper but I got a basic question. How will kexec > know that underlying 32bit machine supports 64bit extensions or not? It looks like /proc/cpuinfo flags contains "lm" (which is long mode, right?) even if the machine is

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

On Fri, 2007-03-16 at 11:40 +0900, Magnus Damm wrote: > Right. And maybe it's a good idea to make sure that this feature is > actually supported by kexec-tools before adding code to the kernel? I sent patches to the fastboot list at the same time I sent these ones to support differences in the und

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

On Fri, 2007-03-16 at 08:48 +0900, Horms wrote: > > > > > > Signed-off-by: Ian Campbell <[EMAIL PROTECTED]> > > > > > > diff --git a/fs/proc/vmcore.c b/fs/proc/vmcore.c > > > index d960507..523e109 100644 > > > --- a/fs/proc/vmcore.c > > > +++ b/fs/proc/vmcore.c > > > @@ -514,7 +514,7 @@ static i

[Fastboot] March '07 kexec-tools-testing Release

Hi, Magnus and I are planning to make a release of kexec-tools-testing in the near future as it seems to have more than enough changes since the last release. To this end the tree is now semi-frozen. *** Please Test! *** If you have anything that you think should go in the release

Re: [Fastboot] [PATCH] [PPC64] Fix wrong max_memory_ranges value

On Wed, Mar 14, 2007 at 03:48:15PM +0100, Bernhard Walle wrote: > The value of max_memory_ranges is calculated in count_memory_ranges() and only > counts the memory@ nodes. However, in get_devtree_details(), pci@ nodes are > also > added to exclude_range just at the end of the loop. > > This patc

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

On Fri, Mar 16, 2007 at 11:40:07AM +0900, Magnus Damm wrote: > On 3/16/07, Horms <[EMAIL PROTECTED]> wrote: > >On Thu, Mar 15, 2007 at 06:56:16PM +0530, Vivek Goyal wrote: > >> On Thu, Mar 15, 2007 at 12:22:57PM +, Ian Campbell wrote: > >> > On Thu, 2007-03-15 at 11:17 +0530, Vivek Goyal wrote:

Re: [Fastboot] [PATCH] kexec-tools: arch_options seems to be unused on sh

On Fri, Mar 16, 2007 at 11:29:36AM +0900, Horms wrote: > arch_options, declared in kexec/arch/sh/kexec-sh.c seems to be unused, > so remove it. > Indeed. > Signed-off-by: Simon Horman <[EMAIL PROTECTED]> > Acked-by: Paul Mundt <[EMAIL PROTECTED]> ___ f

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

On Fri, Mar 16, 2007 at 08:48:08AM +0900, Horms wrote: > On Thu, Mar 15, 2007 at 06:56:16PM +0530, Vivek Goyal wrote: > > On Thu, Mar 15, 2007 at 12:22:57PM +, Ian Campbell wrote: > > > On Thu, 2007-03-15 at 11:17 +0530, Vivek Goyal wrote: > > > > > > But I think changing this macro might run i

Re: [Fastboot] Kexec/kdump got hung

On Thu, Mar 08, 2007 at 07:48:46PM -0800, Dharmosoth Seetharam wrote: > Hi, > > I was able to load the new kenrel(Dump-capture kernel) in the > reserved area by using the following command. > > kexec -l ~seetharam/bin/vmlinux > --initrd=/boot/initrd-2.6.20-Dump-capture-Kernel.img --args-linux

Re: [Fastboot] [PATCH] Kdump is not supported on ppc, s390, sh

On Thu, Mar 15, 2007 at 05:56:46PM +0900, Magnus Damm wrote: > Kdump is not supported on ppc, s390, sh > > So let's return that no crash kernel memory is found. > > Signed-off-by: Magnus Damm <[EMAIL PROTECTED]> Thanks, applied. ___ fastboot mailing li

[Fastboot] [PATCH] kexec-tools: arch_options seems to be unused on sh

arch_options, declared in kexec/arch/sh/kexec-sh.c seems to be unused, so remove it. Signed-off-by: Simon Horman <[EMAIL PROTECTED]> Index: kexec-tools-testing-merge/kexec/arch/sh/kexec-sh.c === --- kexec-tools-testing-merge.orig/kex

Re: [Fastboot] [PATCH] Remove duplicate MAX_LINE

On Thu, Mar 15, 2007 at 05:55:08PM +0900, Magnus Damm wrote: > Remove duplicate MAX_LINE > > MAX_LINE is already defined in kexec/kexec.h > > Signed-off-by: Magnus Damm <[EMAIL PROTECTED]> Thanks, applied. ___ fastboot mailing list fastboot@lists.osdl.

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

On 3/16/07, Horms <[EMAIL PROTECTED]> wrote: > On Thu, Mar 15, 2007 at 06:56:16PM +0530, Vivek Goyal wrote: > > On Thu, Mar 15, 2007 at 12:22:57PM +, Ian Campbell wrote: > > > On Thu, 2007-03-15 at 11:17 +0530, Vivek Goyal wrote: > > > > > > But I think changing this macro might run into issues

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

On Thu, Mar 15, 2007 at 01:42:39PM +, Ian Campbell wrote: > On Thu, 2007-03-15 at 18:56 +0530, Vivek Goyal wrote: > > > > Ideal place for this probably should have been arch dependent > > crash_dump.h file. But we don't have one and no point introducing one > > just for this macro. > > Agree

Re: [Fastboot] [PATCH] Move memory range variables

On 3/15/07, Vivek Goyal <[EMAIL PROTECTED]> wrote: > On Thu, Mar 15, 2007 at 06:11:55PM +0900, Magnus Damm wrote: > > On Thu, 2007-03-15 at 14:30 +0530, Vivek Goyal wrote: > > > On Thu, Mar 15, 2007 at 05:53:19PM +0900, Magnus Damm wrote: > > > > Move memory range variables > > > > > > > > The comm

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

On Thu, Mar 15, 2007 at 01:42:39PM +, Ian Campbell wrote: > On Thu, 2007-03-15 at 18:56 +0530, Vivek Goyal wrote: > > > > Ideal place for this probably should have been arch dependent > > crash_dump.h file. But we don't have one and no point introducing one > > just for this macro. > > Agree

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

On Thu, Mar 15, 2007 at 06:56:16PM +0530, Vivek Goyal wrote: > On Thu, Mar 15, 2007 at 12:22:57PM +, Ian Campbell wrote: > > On Thu, 2007-03-15 at 11:17 +0530, Vivek Goyal wrote: > > > > > But I think changing this macro might run into issues. It is > > > > > being used at few places in kernel,

Re: [Fastboot] [PATCH] Move memory range variables

On Thu, Mar 15, 2007 at 02:53:38PM +0530, Vivek Goyal wrote: > On Thu, Mar 15, 2007 at 06:11:55PM +0900, Magnus Damm wrote: > > On Thu, 2007-03-15 at 14:30 +0530, Vivek Goyal wrote: > > > On Thu, Mar 15, 2007 at 05:53:19PM +0900, Magnus Damm wrote: > > > > Move memory range variables > > > > > > >

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

On Thu, 2007-03-15 at 18:56 +0530, Vivek Goyal wrote: > > Ideal place for this probably should have been arch dependent > crash_dump.h file. But we don't have one and no point introducing one > just for this macro. Agreed. > This change looks good to me. Is there a kdump tree which you'll app

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

On Thu, Mar 15, 2007 at 12:22:57PM +, Ian Campbell wrote: > On Thu, 2007-03-15 at 11:17 +0530, Vivek Goyal wrote: > > > > But I think changing this macro might run into issues. It is > > > > being used at few places in kernel, for example while loading > > > > module. This will essentially mean

[Fastboot] pretty-pretty tvjy Cutie jqj doing blowjob!!

rwrz! pleasing vqg Slut sab at Hardcore Movies!! http://ultimatenebraskaguide.info jyqxg stm joami xifotx. ___ fastboot mailing list fastboot@lists.osdl.org https://lists.osdl.org/mailman/listinfo/fastboot

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

On Thu, 2007-03-15 at 11:17 +0530, Vivek Goyal wrote: > > > But I think changing this macro might run into issues. It is > > > being used at few places in kernel, for example while loading > > > module. This will essentially mean that we allow loading 64bit > > > x86_64 modules on 32bit i386 system

Re: [Fastboot] [PATCH] Move memory range variables

On Thu, Mar 15, 2007 at 06:11:55PM +0900, Magnus Damm wrote: > On Thu, 2007-03-15 at 14:30 +0530, Vivek Goyal wrote: > > On Thu, Mar 15, 2007 at 05:53:19PM +0900, Magnus Damm wrote: > > > Move memory range variables > > > > > > The common kexec code is currently using two global variables to keep

Re: [Fastboot] [PATCH] Move memory range variables

On Thu, 2007-03-15 at 14:30 +0530, Vivek Goyal wrote: > On Thu, Mar 15, 2007 at 05:53:19PM +0900, Magnus Damm wrote: > > Move memory range variables > > > > The common kexec code is currently using two global variables to keep > > track of memory ranges. Other data is kept in a per-instance struct

[Fastboot] [PATCH] Kdump is not supported on ppc, s390, sh

Kdump is not supported on ppc, s390, sh So let's return that no crash kernel memory is found. Signed-off-by: Magnus Damm <[EMAIL PROTECTED]> --- Applies to kexec-tools-testing d6c231c6f341d839fbfb09ea0814dd9a5ccdb005. ppc/kexec-ppc.c |6 +- s390/kexec-s390.c |6 +- sh/kexec-

Re: [Fastboot] [PATCH] Move memory range variables

On Thu, Mar 15, 2007 at 05:53:19PM +0900, Magnus Damm wrote: > Move memory range variables > > The common kexec code is currently using two global variables to keep > track of memory ranges. Other data is kept in a per-instance structure. > This mix is of per-instance and global variables is confu

[Fastboot] [PATCH] Remove duplicate MAX_LINE

Remove duplicate MAX_LINE MAX_LINE is already defined in kexec/kexec.h Signed-off-by: Magnus Damm <[EMAIL PROTECTED]> --- Applies to kexec-tools-testing d6c231c6f341d839fbfb09ea0814dd9a5ccdb005. ia64/crashdump-ia64.c |2 -- sh/kexec-sh.c |1 - 2 files changed, 3 deletions(-)

[Fastboot] [PATCH] Move memory range variables

Move memory range variables The common kexec code is currently using two global variables to keep track of memory ranges. Other data is kept in a per-instance structure. This mix is of per-instance and global variables is confusing and leads to messy code in general. So let's not. This patch move

[Fastboot] gdb is not recognizing the vmcore's symbols

Hi, Finally I am able to get the vmcore on kernel-26.20 using kexec tools. But, While anlysing it through gdb, not getting the proper info. [EMAIL PROTECTED] gdb /usr/u/seetharam/bin/vmlinux-dir/vmlinux-Primary-kernel vmcore/vmcore.3 GNU gdb Red Hat Linux (6.3.0.0-1.21.agamirh) Copyright 2004 F

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

On Thu, Mar 15, 2007 at 11:17:26AM +0530, Vivek Goyal wrote: > On Thu, Mar 15, 2007 at 02:07:56PM +0900, Horms wrote: > > On Thu, Mar 15, 2007 at 10:25:36AM +0530, Vivek Goyal wrote: > > > On Thu, Mar 15, 2007 at 10:46:38AM +0900, Horms wrote: > > > > On Wed, Mar 14, 2007 at 05:00:09PM +, Ian C