Ron Kaye on 30 Jan 2009 05:54:29 -0800


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] 1st kernel panic- HP glich



james:

i think you are right on the money with your advice
will try today.
thanks for the help
never booted to linux rescue before- it was good experience.

ron

This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery.
NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.



James Barrett <jadoba@jadoba.net>
Sent by: plug-bounces@lists.phillylinux.org

01/29/2009 04:40 PM
Please respond to
"Philadelphia Linux User's Group Discussion List"        <plug@lists.phillylinux.org>

To
"Philadelphia Linux User's Group Discussion List" <plug@lists.phillylinux.org>
cc
Subject
Re: [PLUG] 1st kernel panic





The ilo driver is broken in RHEL5.3, and it looks like your problem is
exactly what is being described in this knowledgebase article:

http://kbase.redhat.com/faq/docs/DOC-15564

There is a thread on HP's forum as well:

http://tinyurl.com/dy998s

--
James Barrett

On Thu, Jan 29, 2009 at 4:27 PM, Ron Kaye <rkaye2@csc.com> wrote:
>
> well, now i am doing rhel system build/config/maintain activities for the
> first time.
> as part of my initiation, i had a hp proliant dl360 running RHEL5, deliver
> my first kernel panic.
>
> it was caused by insmod hp_ilo (or something like that)
>
> i get
>
> <0> kernel panic - not synching: Fatal exception
>
> (yes i upgraded the ilo firmware, i turned off the ilo in bios)
>
> where/when is this being loaded?
> i guess i need to edit out a line somewhere.
>
> (didnt find squat in etc/modprobe.conf  where the redhat tech told me to
> look)
>
> any thoughts to get me through my initiation?
> thanks in advance
>
> ron
>
> This is a PRIVATE message. If you are not the intended recipient, please
> delete without copying and kindly advise us by e-mail of the mistake in
> delivery.
> NOTE: Regardless of content, this e-mail shall not operate to bind CSC to
> any order or other contract unless pursuant to explicit written agreement or
> government initiative expressly permitting the use of e-mail for such
> purpose.
> ___________________________________________________________________________
> Philadelphia Linux Users Group         --        http://www.phillylinux.org
> Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
> General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug
>
>
___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug

___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug