Re: Current CVS Kernel Broken on MIPS (010111 - 2.4.0)

Re: Current CVS Kernel Broken on MIPS (010111 - 2.4.0)

[Ian Chilton]

Hello,

> Such a pile of numbers is pretty useless for debuggin unless accompanied
> with the disassembler listing of the crashing code, System.map or even
> better the kernel binary itself ...

Sorry, I forgot..:

http://files.ichilton.co.uk/linux-010111-IP22-4400.tar.gz


It's all in there, ELF + ECOFF + System.map


Thanks!


Bye for Now,

Ian


                                \|||/ 
                                (o o)
 /---------------------------ooO-(_)-Ooo---------------------------\
 |  Ian Chilton        (IRC Nick - GadgetMan)     ICQ #: 16007717  |
 |-----------------------------------------------------------------|
 |  E-Mail: ian@ichilton.co.uk     Web: http://www.ichilton.co.uk  |
 |-----------------------------------------------------------------|
 |         Budget: A method for going broke methodically.          |
 \-----------------------------------------------------------------/

Re: Current CVS Kernel Broken on MIPS (010111 - 2.4.0)

[Ralf Baechle]

On Thu, Jan 11, 2001 at 10:57:01PM +0000, Ian Chilton wrote:

> > Such a pile of numbers is pretty useless for debuggin unless accompanied
> > with the disassembler listing of the crashing code, System.map or even
> > better the kernel binary itself ...
> 
> Sorry, I forgot..:
> 
> http://files.ichilton.co.uk/linux-010111-IP22-4400.tar.gz
> 
> 
> It's all in there, ELF + ECOFF + System.map

It's a crash during the very early initialization of the kernel, that is
before trap_init() gets called.  __alloc_bootmem_core calls memset with
bogus addresses and that again crashes.  Not very much else I can read
from this crash and not very much I can do without an Indy ...

  Ralf

Current CVS Kernel Broken on MIPS (010111 - 2.4.0)

[Ian Chilton]

Hello,

Klaus tried booting the kernel I compiled using current CVS (010111)

I used the same GCC 2.95.2 + Binutils 2.10.1 that worked when compiling
001027.

This output was from an I2

Command Monitor.  Type "exit" to return to the menu.
>> bootp():vmlinux console=ttyS0
Setting $netaddr to 192.168.1.2 (from server scotty)
Obtaining vmlinux from server scotty
  \
Exception: <vector=Normal>
Status register: 0x10044803<CU0,CH,IM7,IM4,IPL=???,MODE=KERNEL,EXL,IE>
Cause register: 0x3000c01c<CE=3,IP8,IP7,EXC=DBE>
Exception PC: 0x88141554, Exception RA: 0x881821d4
Data Bus error GIO Timeout Interrupt
Local I/O interrupt register 1: 0x80 <VR/GIO2>
Local I/O interrupt register 2: 0xca <EISA,SLOT0,SLOT1>
GIO parity error register: 0x400<TIME>
GIO bus error: address: 0x1000000
  Saved user regs in hex (&gpda 0xa8740e48, &_regs 0xa8741048):
  arg: a8740000 0 81009400 1000
  tmp: a8740000 100a 81000000 881abe50 100a 1 9400 20
  sve: a8740000 0 0 0 0 0 0 0
  t8 a8740000 t9 0 at 0 v0 0 v1 0 k1 81000000
  gp a8740000 fp 0 sp 0 ra 0

PANIC: Unexpected exception

[Press reset or ENTER to restart.]


Bye for Now,

Ian


                                \|||/ 
                                (o o)
 /---------------------------ooO-(_)-Ooo---------------------------\
 |  Ian Chilton        (IRC Nick - GadgetMan)     ICQ #: 16007717  |
 |-----------------------------------------------------------------|
 |  E-Mail: ian@ichilton.co.uk     Web: http://www.ichilton.co.uk  |
 |-----------------------------------------------------------------|
 |         Budget: A method for going broke methodically.          |
 \-----------------------------------------------------------------/

Re: Current CVS Kernel Broken on MIPS (010111 - 2.4.0)

[Ralf Baechle]

On Thu, Jan 11, 2001 at 10:42:05PM +0000, Ian Chilton wrote:

> I used the same GCC 2.95.2 + Binutils 2.10.1 that worked when compiling
> 001027.
> 
> This output was from an I2
> 
> Command Monitor.  Type "exit" to return to the menu.
> >> bootp():vmlinux console=ttyS0
> Setting $netaddr to 192.168.1.2 (from server scotty)
> Obtaining vmlinux from server scotty
>   \
> Exception: <vector=Normal>
> Status register: 0x10044803<CU0,CH,IM7,IM4,IPL=???,MODE=KERNEL,EXL,IE>
> Cause register: 0x3000c01c<CE=3,IP8,IP7,EXC=DBE>
> Exception PC: 0x88141554, Exception RA: 0x881821d4
> Data Bus error GIO Timeout Interrupt
> Local I/O interrupt register 1: 0x80 <VR/GIO2>
> Local I/O interrupt register 2: 0xca <EISA,SLOT0,SLOT1>
> GIO parity error register: 0x400<TIME>
> GIO bus error: address: 0x1000000
>   Saved user regs in hex (&gpda 0xa8740e48, &_regs 0xa8741048):
>   arg: a8740000 0 81009400 1000
>   tmp: a8740000 100a 81000000 881abe50 100a 1 9400 20
>   sve: a8740000 0 0 0 0 0 0 0
>   t8 a8740000 t9 0 at 0 v0 0 v1 0 k1 81000000
>   gp a8740000 fp 0 sp 0 ra 0

Such a pile of numbers is pretty useless for debuggin unless accompanied
with the disassembler listing of the crashing code, System.map or even
better the kernel binary itself ...

  Ralf