linux-mips
[Top] [All Lists]

Re: Kernel crash on boot with current cvs (todays)

To: Keith Owens <kaos@ocs.com.au>
Subject: Re: Kernel crash on boot with current cvs (todays)
From: Florian Lohoff <flo@rfc822.org>
Date: Mon, 11 Jun 2001 21:12:51 +0200
Cc: linux-mips@oss.sgi.com
In-reply-to: <10206.992231584@ocs4.ocs-net>; from kaos@ocs.com.au on Mon, Jun 11, 2001 at 01:53:04PM +1000
Organization: rfc822 - pure communication
References: <20010611000359.A25631@paradigm.rfc822.org> <10206.992231584@ocs4.ocs-net>
Sender: owner-linux-mips@oss.sgi.com
User-agent: Mutt/1.3.15i
On Mon, Jun 11, 2001 at 01:53:04PM +1000, Keith Owens wrote:
> On Mon, 11 Jun 2001 00:03:59 +0200, 
> Florian Lohoff <flo@rfc822.org> wrote:
> >i just tried to boot an Indy of mine with the current cvs (from this
> >morning) and it crashes 
> >
> >ksymoops 2.4.1 on i686 2.2.18ext3.  Options used
> >Using defaults from ksymoops -t elf32-little -a unknown
> >Error (Oops_bfd_perror): scan_arch for specified architecture Success
> 
> I cannot help with the oops but your ksymoops run has problems.  When
> doing cross system oops debugging, you need to specify the target
> machine and architecture with the -t and -a flags.  Otherwise ksymoops 
> defaults to the current machine.  Adding -t and -a will fix the above
> error and decode the code: line.

Nope - it wont as it strictly uses the /usr/bin/objdump - You have to
set the environment var "KSYMOOPS_OBJDUMP"

Flo
-- 
Florian Lohoff                  flo@rfc822.org             +49-5201-669912
     Why is it called "common sense" when nobody seems to have any?


<Prev in Thread] Current Thread [Next in Thread>