grubby recieved SIGSEGV! Backtrace (6):

[Justin P. Mattock]

Michael Schwendt wrote:
> On Thu, 30 Jul 2009 15:54:24 -0700, Justin wrote:
>
>    
>> After a nice install, and compiling of the latest git
>> everything went smoothly.
>>
>> Then I decided to recompile the kernel with
>> fedoras .config instead of mine.
>> went pretty good, but then after I went in and removed
>> the old System.map, and vmlinuz from my initial install
>> (then make install etc..)
>> this appeared:
>> sudo make install:
>>
>>
>> sh /home/name/packages/kernel/2.6.31/arch/x86/boot/install.sh
>> 2.6.31-rc4-00295-g608ae20 arch/x86/boot/bzImage \
>> 		System.map "/boot"
>> grubby recieved SIGSEGV!  Backtrace (6):
>> /sbin/grubby[0x40793f]
>> /lib64/libc.so.6[0x3674833370]
>> /sbin/grubby[0x40211c]
>> /sbin/grubby[0x407392]
>> /lib64/libc.so.6(__libc_start_main+0xfd)[0x367481ea2d]
>> /sbin/grubby[0x4018f9]
>>
>> seems to be broken after this.
>>
>> Any ideas?
>>      
>
>
> http://bugz.fedoraproject.org/grubby
>
> If it's not known already, run "debuginfo-install grubby" as
> root user, reproduce the crash, and submit a detailed backtrace
> in bugzilla. The "Report..." link at the posted address makes it
> very easy to file new tickets in bugzilla.
>
> Help on getting detailed backtraces:
> http://fedoraproject.org/wiki/StackTraces
>
>    
opps!!
I guess it helps to have ext4 compiled in the kernel..
(sh^t I'm a neewbie)..

Justin P. Mattock