From: Sunil Mushran <Sunil.Mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Strange panics on ocfs2-1.2 svn rev 2988:2990
Date: Thu Mar 15 15:28:29 2007 [thread overview]
Message-ID: <45F9C88A.3010307@oracle.com> (raw)
In-Reply-To: <45F9C0E3.8040803@terra.com.br>
If your issue is as to why the server is not rebooting (leaving aside
the cause of the oops), check the following values.
$ cat /proc/sys/kernel/panic_on_oops
1
$ cat /proc/sys/kernel/panic
30
As in, it should be set to panic on oops and set some time for machine
restart.
Marcus Alves Grando wrote:
> Sunil Mushran wrote:
>
>> You'll have to be lot more specific.... especially considering you are
>> working directly of an svn tree. For starters, where is the server hung?
>>
>
> Ok It's true.
>
> Let's start again.
>
> After make svn up and make packages with svn rev 2990. Two servers
> doesn't reboot after "shutdown -r now". After look on console both
> servers have panic message.
>
> Two panic's attached.
>
> Thanks
>
>
>> Marcus Alves Grando wrote:
>>
>>> Hi developers,
>>>
>>> After svn up ocfs2-1.2 tree from 2987 to 2990 i have strange problems.
>>> My servers are four RH AS4u4 with kernel-hugemem. When i execute
>>> "shutdown -r now" in four server some servers reboot some not, with and
>>> without changing idle_timeout_ms.
>>>
>>> Any fix for that?
>>>
>>> Regards
>>>
>>>
>>>
>
>
prev parent reply other threads:[~2007-03-15 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 14:04 [Ocfs2-devel] Strange panics on ocfs2-1.2 svn rev 2988:2990 Marcus Alves Grando
2007-03-15 14:11 ` Sunil Mushran
2007-03-15 14:55 ` Marcus Alves Grando
2007-03-15 15:23 ` Sunil Mushran
2007-03-15 15:28 ` Marcus Alves Grando
2007-03-15 15:43 ` Sunil Mushran
2007-03-15 15:28 ` Sunil Mushran [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45F9C88A.3010307@oracle.com \
--to=sunil.mushran@oracle.com \
--cc=ocfs2-devel@oss.oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.