X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8587C.05704503@onstor-exch02.onstor.net>; Wed, 16 Jan 2008 13:11:47 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: kernel panic ?
Date: Wed, 16 Jan 2008 13:11:46 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E07AE236D@onstor-exch02.onstor.net>
In-Reply-To: <20080116120936.1c4a80e7@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: kernel panic ?
Thread-Index: AchYe7fT+5rQVDl8T0GUdowW291+lAAACNfg
From: "Vikas Saini" <vikas.saini@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "dl-Cougar" <dl-Cougar@onstor.com>

Looks like there was a FP crash around same time as kernel panic. I will
add this to defect.


Jan 16 11:46:58 g12r10 : 1:2:evm:WARNING: 1089: [][]: 2 I/O retries for
volume[g12r10-raj-vs2-vol01].
Jan 16 11:47:01 g12r10 kernel: fp0: 1090: [][]: 2 I/O retries for
volume[g12r10-raj-vs2-vol01].
Jan 16 11:47:01 g12r10 : 1:2:evm:WARNING: 1090: [][]: 2 I/O retries for
volume[g12r10-raj-vs2-vol01].
Jan 16 11:47:15 g12r10 kernel: fp0: 1091: [][]: 3 I/O retries for
volume[g12r10-raj-vs2-vol01].
Jan 16 11:47:15 g12r10 : 1:2:evm:WARNING: 1091: [][]: 3 I/O retries for
volume[g12r10-raj-vs2-vol01].
Jan 16 11:47:24 g12r10 kernel: tx0: passive crash handler: continuing in
debug mode
Jan 16 11:47:24 g12r10 kernel: tx1: passive crash handler: continuing in
debug mode
Jan 16 11:47:24 g12r10 kernel: fp0: passive crash handler: continuing in
debug mode
Jan 16 11:47:24 g12r10 kernel: fp0: cpu 5 crashed, core 3
Jan 16 11:47:24 g12r10 kernel: fp1: passive crash handler: continuing in
debug mode
Jan 16 11:47:24 g12r10 kernel: fp1: cpu 5 crashed, core 3
Jan 16 11:47:24 g12r10 kernel: tx0: cpu 5 crashed, core 3
Jan 16 11:47:24 g12r10 kernel: tx1: cpu 5 crashed, core 3
Jan 16 11:47:24 g12r10 kernel: tx0: Autoreboot "off", stopping in debug
mode
Jan 16 11:47:24 g12r10 kernel: tx1: Autoreboot "off", stopping in debug
mode
Jan 16 11:47:24 g12r10 kernel: fp0: Autoreboot "off", stopping in debug
mode
Jan 16 11:47:24 g12r10 kernel: fp1: Autoreboot "off", stopping in debug
mode
Jan 16 11:47:24 g12r10 kernel: fp3:
Jan 16 11:47:24 g12r10 kernel: fp3:
Jan 16 11:47:24 g12r10 kernel: fp3: Exception Cause =3D Watchdog
Timeout/NMI
Jan 16 11:47:24 g12r10 kernel: fp3: ERREPC:   0xffffffff8305261c
Jan 16 11:47:24 g12r10 kernel: fp3: RA:       0xffffffff83050234
Jan 16 11:47:24 g12r10 kernel: fp3: SR:       0x20086fa1
Jan 16 11:47:24 g12r10 kernel: fp3: NMI : Watchdog Timeout NMI
Jan 16 11:47:24 g12r10 kernel: fp3: Image Version : NFP_FP :
R4.0.0.DEV-CGDBG-011408 : Mon Jan 14 12:52:22 2008
Jan 16 11:47:24 g12r10 kernel: fp3: PROM Version  : PROM_SIBYTE_CG :
Cougar-prom-1.0.2 : Fri Dec 14 11:53:50 2007
Jan 16 11:47:24 g12r10 kernel: fp3: Boot Time  : Wed Jan 16 03:13:28 GMT
2008
Jan 16 11:47:24 g12r10 kernel: fp3: Crash Time : Wed Jan 16 11:47:20 GMT
2008
Jan 16 11:47:24 g12r10 kernel: fp3: core_dump_open 0 0
Jan 16 11:47:24 g12r10 kernel: fp3: Can not open core file
Jan 16 11:47:24 g12r10 kernel: fp3: Autoreboot "off", stopping in debug
mode


-----Original Message-----
From: Andy Sharp=20
Sent: Wednesday, January 16, 2008 12:10 PM
To: Vikas Saini
Cc: dl-Cougar
Subject: Re: kernel panic ?

The panic should have been fully logged in /var/log/messages.  But the
error is plain to see: the management bus code has gotten ahold of a
bogus address.  But file a bug and include the stack trace
from /var/log/messages.  If you need assistance, you know where my
doorbell is ~:^)

Cheers,

a

On Wed, 16 Jan 2008 12:05:00 -0800 "Vikas Saini"
<vikas.saini@onstor.com> wrote:

> Do we have any logs which can provide more info about it.
>=20
> =20
>=20
> Thanks
>=20
> Vikas
>=20
> =20
>=20
> =20
>=20
> =20
>=20
> Jan 16 11:46:01 g12r10 : 1:2:evm:WARNING: 1079: [][]: 2 I/O retries
> for volume[g12r10-raj-vs2-vol01].
>=20
> Jan 16 11:46:02 g12r10 : 1:2:evm:WARNING: 1080: [][]: 2 I/O retries
> for volume[g12r10-raj-vs2-vol01].
>=20
> Jan 16 11:46:13 g12r10 : 1:2:evm:WARNING: 1081: [][]: 2 I/O retries
> for volume[g12r10-raj-vs2-vol01].
>=20
> Jan 16 11:46:28 g12r10 : 1:2:evm:WARNING: 1082: [][]: 2 I/O retries
> for volume[g12r10-raj-vs2-vol01].
>=20
> Jan 16 11:46:35 g12r10 : 1:2:evm:WARNING: 1083: [][]: 2 I/O retries
> for volume[g12r10-raj-vs2-vol01].
>=20
> Jan 16 11:46:40 g12r10 : 1:2:evm:WARNING: 1084: [][]: 2 I/O retries
> for volume[g12r10-raj-vs2-vol01].
>=20
> Jan 16 11:46:44 g12r10 : 1:2:evm:WARNING: 1085: [][]: 2 I/O retries
> for volume[g12r10-raj-vs2-vol01].
>=20
> Jan 16 11:46:45 g12r10 : 1:2:evm:WARNING: 1086: [][]: 2 I/O retries
> for volume[g12r10-raj-vs2-vol01].
>=20
> Jan 16 11:46:51 g12r10 : 1:2:evm:WARNING: 1087: [][]: 2 I/O retries
> for volume[g12r10-raj-vs2-vol01].
>=20
> Jan 16 11:46:55 g12r10 : 1:2:evm:WARNING: 1088: [][]: 2 I/O retries
> for volume[g12r10-raj-vs2-vol01].
>=20
> Jan 16 11:46:58 g12r10 : 1:2:evm:WARNING: 1089: [][]: 2 I/O retries
> for volume[g12r10-raj-vs2-vol01].
>=20
> Jan 16 11:47:01 g12r10 : 1:2:evm:WARNING: 1090: [][]: 2 I/O retries
> for volume[g12r10-raj-vs2-vol01].
>=20
> Jan 16 11:47:15 g12r10 : 1:2:evm:WARNING: 1091: [][]: 3 I/O retries
> for volume[g12r10-raj-vs2-vol01].
>=20
> Kernel panic - not syncing: MGMTBUS_PHYS2VIRT: invalid phys addr 1
>=20
> Rebooting in 5 seconds..<2>SiByte Watchdog in danger of initiating
> system reset in 3.6 seconds
>=20
> SiByte Watchdog in danger of initiating system reset in 3.6 seconds
>=20
> =20
>=20
> =20
>=20
> =20
>=20
> PowerOn Self Test........OK
>=20
> =20
>=20
> Initializing System......please wait
>=20
> =20
>=20
> =20
>=20
> =20
>=20
> =20
>=20
> =20
>=20
> PMON [SSC,EL,FP,64]
>=20
> ONStor Inc. PROM_SIBYTE_CG : Cougar-prom-1.0.2 : Fri Dec 14 11:53:50
> 2007
>=20
> CPU type SB1125.  Rev 35  600 MHz
>=20
> module: SSC, Slot 0, CPU 0
>=20
> Memory size 512 MB.
>=20
> Icache size  32 KB, 32/line (4 way)
>=20
> Dcache size  32 KB, 32/line (4 way)
>=20
> Scache size 256 KB, 32/line  (4 way)
>=20
> debug IP addr =3D 10.2.10.12
>=20
> debug IP mask =3D 255.255.0.0
>=20
> =20
>=20
> =20
>=20
> Initializing Autoloader, hit control-E to bypass
>=20
>
........................................................................
> ........
>=20
> =20
>=20
> Type ctrl-e to stop autoload.
>=20
> Waiting for SSC to enter autoload init state...done.
>=20
> tftp server addr =3D 10.2.0.4
>=20
> load, ip addr =3D 0xa020004, fname =3D 10.2.10.12/vmlinux.bin
>=20
> loading 10.2.10.12/vmlinux.bin from 0xa020004 at 0xffffffff82000000
>=20
> tpl_findBindCb prot=3D17 lport=3D9736
>=20
> tpl_allocBindCb
>=20
> tftp_tplAddConnInd
>=20
> TFTP transfer completed.
>=20
> tftp_tplDelConnInd
>=20
> binary load, 3079568 bytes (0x2efd90)
>=20
> Type ctrl-e to stop autoload.
>=20
> Waiting for TXRX to enter autoload init state...done.
>=20
> tftp server addr =3D 10.2.0.4
>=20
> load, ip addr =3D 0xa020004, fname =3D 10.2.10.12/txrx_cg.bin
>=20
> loading 10.2.10.12/txrx_cg.bin from 0xa020004 at 0x42000000
>=20
> tftp_tplAddConnInd
>=20
> TFTP transfer completed.
>=20
> tftp_tplDelConnInd
>=20
> binary load, 10047456 bytes (0x994fe0)
>=20
