RH Enterprise ES release 4 (Nahant Update 1) kernel panic

[David Tonhofer, m-plify S.A.]

--On Tuesday, December 27, 2005 11:50 AM -0500 KC <ask at peter-angela.com> wrote:

> Hi all
>
> We are running the "Red Hat Enterprise Linux ES release 4 (Nahant
> Update 1)" kernel  2.6.9-11.ELsmp in the machine
> 2 x AMD Dual Core AMD Opteron(tm) Processor 275, 8G memory, K8N-DRE
> motherboard
>
> This machine was running 7 days. but those 2 days, the server has
> kernel panic in twice and last top command was showing 56.93
> CPU1 took about 79.8%, other 3 CPUs were almost 0%
>
> have you had any experience about it?
>
> and how can we find out the problem coming from?
>


Hi,

Try bugzilla.redhat.com with an appropriate query, like this:

<https://bugzilla.redhat.com/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Red+Hat+Enterprise+Linux&version=4&version=4.0&component=kernel&component_text=&query_format=advanced&bug_status=NEW&bug_status=VERIFIED&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=CLOSED&bug_status=NEEDINFO&bug_status=MODIFIED&bug_status=ASSIGN_TO_PM&bug_status=INVESTIGATE&bug_status=SPEC&bug_status=ON_DEV&bug_status=QA_READY&bug_status=ON_QA&bug_
status=PROD_READY&bug_status=FAILS_QA&bug_status=UNCONFIRMED&bug_status=NEEDINFO_REPORTER&bug_status=NEEDINFO_PM&bug_status=NEEDINFO_ENG&bug_status=PASSES_QA&bug_status=RELEASE_PENDING&bug_status=POST&bug_status=NEEDINFO_QA&bug_severity=high&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&fixed_in_type=allwordssubstr&fixed_in=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&e
mailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=>

(ok, so this is not too readable, it selects high severity errors in the kernel
component in RH ES 4 in any report state)

...maybe there is something in there that might help.

You should also try to upgrade to a later kernel.

Best regards,

 -- David