X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7F97C.1748FAD4@onstor-exch02.onstor.net>; Mon, 17 Sep 2007 14:42:56 -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: DHCP boot stuck in panic loop
Date: Mon, 17 Sep 2007 14:42:56 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E05963313@onstor-exch02.onstor.net>
In-Reply-To: <20070917151745.45458184@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: DHCP boot stuck in panic loop
Thread-Index: Acf5eJNMMqh8JtATR16a3bcavDo92wAAwmoA
References: <20070917151745.45458184@ripper.onstor.net>
From: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	<dl-cougar>,
	"Mike Lee" <mike.lee@onstor.com>

I think Linux kernel gods (or daemons) just don't like Mike.

If you give me your bobcat, I can try booting it.

>-----Original Message-----
>From: Andy Sharp
>Sent: Monday, September 17, 2007 3:18 PM
>To: dl-cougar
>Subject: Fw: DHCP boot stuck in panic loop
>
>Something wrong with the kernel you have?
>
>Begin forwarded message:
>
>Date: Mon, 17 Sep 2007 15:12:47 -0700
>From: "Mike Lee" <mike.lee@onstor.com>
>To: "Larry Scheer" <larry.scheer@onstor.com>
>Cc: "Tim Gardner" <tim.gardner@onstor.com>, "Andy Sharp"
><andy.sharp@onstor.com> Subject: DHCP boot stuck in panic loop
>
>
>
>Hi Larry:
>
>Eng52 gets stuck in a kernel panic loop when I try to boot off of DHCP.
>The log is attached; it looks like that things went south, when the
>following appeared:
>
>
>Unknown ARP type 0xfffe for device mgmtbus
>
>CPU 0 Unable to handle kernel paging request at virtual address
>00000005, epc =3D=3D 83171488, ra =3D=3D 83183634
>
>For now, I will try to change eng52 back to boot from disk, and see if
>I can trade it with someone who has another bobcat. Also, I will
>compare my boot log with the one you sent me.
>
>Please let me know if you can think of something else to try.  Thanks
>again!
>
>-Mike
