From: gspujar@hss.hns.com
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, achowdhry@hss.hns.com
Subject: Re: software watchdog: it works
Date: Tue, 11 Dec 2001 18:37:13 +0530 [thread overview]
Message-ID: <65256B1F.0047CC75.00@sandesh.hss.hns.com> (raw)
Hi,
Thanks a lot for your help. I modified the softdog code and I get the message
logged in my log file on system reboot.
Thanks
Girish
Russell King <rmk@arm.linux.org.uk> on 12/11/2001 05:20:59 PM
To: Girish S Pujar/HSS@HSS
cc: linux-kernel@vger.kernel.org, Atul Chowdhry/HSS@HSS
Subject: Re: software watchdog
On Tue, Dec 11, 2001 at 04:26:07PM +0530, gspujar@hss.hns.com wrote:
> Why is that the printk output not going to syslog although I have entry in
> /etc/syslog.conf
>
> kern.crit /var/log/pbsc.log
> even after I remove the mdelay call.
The machine reboots before syslog gets to run.
What happens is:
printk();
reboot();
During that period, syslog is unable to run, and therefore is unable to
write the log message to disk.
> Does it mean that without using "testing" mode ( I cannot beacuse I need a
> reboot) it is not possible to get log ?
I suppose you could modify softdog to delay the reboot using it's timer
(the timer fires the first time, you check data to see if it's non-zero.
If it's not, increment watchdog_ticktock.data, and set the watchdog to
timeout in 5 seconds, return).
You should probably prevent softdog_write updating the timer if the
data field is non-zero, so once you don't change the behaviour; this
is of course dependent on your test case.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
reply other threads:[~2001-12-11 13:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=65256B1F.0047CC75.00@sandesh.hss.hns.com \
--to=gspujar@hss.hns.com \
--cc=achowdhry@hss.hns.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®