From: "Denys Fedoryshchenko" <denys@visp.net.lb>
To: Len Brown <lenb@kernel.org>
Cc: linux-kernel@vger.kernel.org, wim@iguana.be
Subject: Re: kernel panic on 2.6.24/iTCO_wdt not rebooting machine
Date: Fri, 1 Feb 2008 21:15:07 +0200 [thread overview]
Message-ID: <20080201191048.M59862@visp.net.lb> (raw)
In-Reply-To: <200802011211.42089.lenb@kernel.org>
On Fri, 1 Feb 2008 12:11:41 -0500, Len Brown wrote
>
> What do you see if you build with CONFIG_HIGH_RES_TIMERS=n
>
> Does it work better if you boot with "acpi=off"?
> if yes, how about with just pnpacpi=off?
>
> thanks,
> -Len
It is not very easy to test. About bug - most probably it is related to third
party ESFQ patch, i will drop it and then test more properly when i will be
able to make watchdog work fine. But more important i notice - that iTCO_wdt
is not working at all. I think hrtimers doesn't change anything on that.
About testing, i cannot take even small risk now(and near 3-5 days) by
changing kernel options, i set now maximum available set of watchdogs, cause
there is noone to maintain server, area is unreachable because of snow and
bad weather.
Do you think reasonable to try acpi / pnpacpi with iTCO_wdt to make it work?
Maybe just registers addresses or way how TCO watchdog activated changed on
this chipset?
--
Denys Fedoryshchenko
Technical Manager
Virtual ISP S.A.L.
next prev parent reply other threads:[~2008-02-01 19:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 15:12 kernel panic on 2.6.24/iTCO_wdt not rebooting machine Denys Fedoryshchenko
2008-02-01 17:11 ` Len Brown
2008-02-01 19:15 ` Denys Fedoryshchenko [this message]
2008-02-01 20:39 ` Len Brown
2008-02-02 0:44 ` Denys Fedoryshchenko
2008-02-02 4:18 ` Denys Fedoryshchenko
2008-02-02 18:38 ` Wim Van Sebroeck
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=20080201191048.M59862@visp.net.lb \
--to=denys@visp.net.lb \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wim@iguana.be \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox