Thanks a lot for your help. I modified the softdog code and I get the message
logged in my log file on system reboot.
Russell King <firstname.lastname@example.org> on 12/11/2001 05:20:59 PM
To: Girish S Pujar/HSS@HSS
cc: email@example.com, Atul Chowdhry/HSS@HSS
Subject: Re: software watchdog
On Tue, Dec 11, 2001 at 04:26:07PM +0530, firstname.lastname@example.org wrote:
> Why is that the printk output not going to syslog although I have entry in
> kern.crit /var/log/pbsc.log
> even after I remove the mdelay call.
The machine reboots before syslog gets to run.
What happens is:
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 (email@example.com) The developer of ARM Linux http://www.arm.linux.org.uk/personal/aboutme.html
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:20 EST