From: Russell King <rmk@arm.linux.org.uk>
To: gspujar@hss.hns.com
Cc: linux-kernel@vger.kernel.org, achowdhry@hss.hns.com
Subject: Re: software watchdog
Date: Tue, 11 Dec 2001 11:50:59 +0000 [thread overview]
Message-ID: <20011211115059.A3740@flint.arm.linux.org.uk> (raw)
In-Reply-To: <65256B1F.003BCCC1.00@sandesh.hss.hns.com>
In-Reply-To: <65256B1F.003BCCC1.00@sandesh.hss.hns.com>; from gspujar@hss.hns.com on Tue, Dec 11, 2001 at 04:26:07PM +0530
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
next prev parent reply other threads:[~2001-12-11 11:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 10:56 software watchdog gspujar
2001-12-11 11:50 ` Russell King [this message]
2001-12-11 18:48 ` Oliver Xymoron
-- strict thread matches above, loose matches on Subject: below --
2001-12-11 8:03 gspujar
2001-12-11 8:17 ` J Sloan
2001-12-11 10:08 ` Russell King
2001-11-02 6:08 gspujar
2001-11-02 18:52 ` Alberto Bertogli
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=20011211115059.A3740@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=achowdhry@hss.hns.com \
--cc=gspujar@hss.hns.com \
--cc=linux-kernel@vger.kernel.org \
/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