kdb
[Top] [All Lists]

Re: PATCH: kdb for 2.6.13 x86_64

To: Ray Bryant <raybry@xxxxxxxxxxxxxxxxx>
Subject: Re: PATCH: kdb for 2.6.13 x86_64
From: Jack F Vogel <jfv@xxxxxxxxxxxx>
Date: Wed, 31 Aug 2005 11:33:11 -0700
Cc: kdb@xxxxxxxxxxx
In-reply-to: <200508311548.14108.raybry@mpdtxmail.amd.com>
References: <20050830181626.GA14100@trane.bluesong.net> <22067.1125449056@ocs3.ocs.com.au> <20050831023320.GA5881@trane.bluesong.net> <200508311548.14108.raybry@mpdtxmail.amd.com>
Reply-to: jfv@xxxxxxxxxxxx
Sender: kdb-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.6i
On Wed, Aug 31, 2005 at 03:48:13PM -0500, Ray Bryant wrote:
> 
> If I turn off kdb_modules, 2.6.13 plus your patch and the common kdb patch 
> compiles, boots, and passes an initial sniff test.  This is on a 4 socket, 
> dual core Opteron.
> 
> I haven't investigated further as to why turning on kdb_modules results in 
> something that fails during link with the messages:
> 
> BFD: Warning: Writing section `.kdb_initcall.init' to huge (ie negative) file 
> offset 0xffffffff8058efc0.
> objcopy: arch/x86_64/boot/compressed/vmlinux.bin: File truncated
> make[2]: *** [arch/x86_64/boot/compressed/vmlinux.bin] Error 1
> make[1]: *** [arch/x86_64/boot/compressed/vmlinux] Error 2
> make: *** [bzImage] Error 2

Hmm, I dont normally have modules defined anyway, but that is
odd. So this didnt happen with the 2.6.11 kernel?

If no one here has any ideas about this we should ask in LKML
I think.

Thanks for the testing Ray :)

Jack

---------------------------
Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
<Prev in Thread] Current Thread [Next in Thread>