X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C83130.AE0A3001@onstor-exch02.onstor.net>; Tue, 27 Nov 2007 12:04:12 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: system reboot from the nfxsh Oopses the Kernel
Date: Tue, 27 Nov 2007 12:04:12 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E056C91CF@onstor-exch02.onstor.net>
In-Reply-To: <20071127120324.066f1340@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: system reboot from the nfxsh Oopses the Kernel
Thread-Index: AcgxMJFTaEwu/mLhQIij7qB4V4DliAAABIuA
From: "Larry Scheer" <larry.scheer@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

Thanks, I will let them know.

-----Original Message-----
From: Andy Sharp=20
Sent: Tuesday, November 27, 2007 12:03 PM
To: Larry Scheer
Cc: Tim Gardner; Rendell Fong; Maxim Kozlovsky
Subject: Re: system reboot from the nfxsh Oopses the Kernel

Larry, any time you see write_mipsphys or read_mipsphys in the stack
trace, just go ahead and notify max and rendell.  This is a problem in
chassisd or something that opens and uses mipsphys device.

On Tue, 27 Nov 2007 11:45:51 -0800 "Larry Scheer"
<larry.scheer@onstor.com> wrote:

> Andy,
>     Would you like me to file a defect?
> This happens whenever I do a system reboot from the nfxsh:
>=20
> eng216:~# CPU 0 Unable to handle kernel paging request at virtual
> address 500000f0, epc =3D=3D 83126d30, ra =3D=3D 83126d20
> Oops[#1]:
> Cpu 0
> $ 0   : 00000000 7f89c900 500000f0 00000001
> $ 4   : 8c0e3ec0 7f89c900 00000000 b00000f0
> $ 8   : 00000001 8c0e3ec0 00000000 00000000
> $12   : 8df1c800 00000004 8c0e3f40 00404ba8
> $16   : 8df1c800 00000004 7f89c8fc 8c0e3f40
> $20   : 00000004 004016b0 2ac87ee0 00538b48
> $24   : 00000000 2adad84c                 =20
> $28   : 8c0e2000 8c0e3eb8 7f89c870 83126d20
> Hi    : 000000f9
> Lo    : 0003a515
> epc   : 83126d30 write_mipsphys+0x70/0x138     Not tainted
> ra    : 83126d20 write_mipsphys+0x60/0x138
> Status: b000ef03    KERNEL EXL IE=20
> Cause : 0080000c
> BadVA : 500000f0
> PrId  : 00003440
> Modules linked in: autofs4 softdog
> Process chassis (pid: 2102, threadinfo=3D8c0e2000, task=3D8cef6000)
> Stack : 00000001 00000001 8d10d248 83783000 830731d0 830731a8 83070584
> 00000000
>         00000020 8df1c800 83783000 00000006 8df1c800 ffffffe3 00000004
> 7f89c8fc
>         83073afc 83070ae4 830606c8 00100873 00000000 2aafef10 00000000
> 00406f44
>         00000006 7f89c8fc b00000f0 00000000 8300a5e0 8300a5e0 2ac87ee0
> 7f92e1fc
>         004d5d90 0000002f b00000f0 00000000 00000000 b000ef00 00001069
> 00000000
>         ...
> Call Trace:
> [<83126d30>] write_mipsphys+0x70/0x138
> [<830731d0>] vfs_write+0xc0/0x160
> [<83073afc>] sys_pwrite64+0x94/0xac
> [<8300a5e0>] stack_done+0x20/0x3c
>=20
>=20
> Code: 8fa30004  3c02a000  00e21021 <ac430000> 8dc60000  00002821
> 8dc70004  01a04821  00cd1021=20
>=20
> Broadcast message from root@eng216 (pts/0) (Tue Nov 27 11:42:30 2007):
>=20
> The system is going down for reboot NOW!
