watchdogd coredump
Xin Li
delphij at delphij.net
Sat Nov 3 22:33:39 UTC 2012
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 11/3/12 3:13 PM, Garrett Cooper wrote:
> On Sat, Nov 3, 2012 at 2:55 PM, Alexander Leidinger
> <Alexander at leidinger.net <mailto:Alexander at leidinger.net>> wrote:
>
> Hi,
>
> I updated from r239708 to r242511 and my watchdogd coredumps (and
> brings down the system... well, the WD works).
>
> Before I have a deeper look (recompiling with debugging and such)
> at this, can someone confirm that with a recent -current and a WD
> configured to call a shell script which does a simple ls to
> /dev/null there is a segfault in watchdogd?
>
> watchdogd_flags="-e /root/bin/wd_check.sh -s 5 -t 60"
[...] ^^
> Do you have watchdogd_flags set to something non-standard? Xin
> CCed since he made the last commit.
I think my commit have nothing to do with Alexander's issue, it's
fairly self-contained with no outreaching memory access that could
cause access violation.
I think Kostik was right that he may be running an older version of
kernel with watchdog newer than 239896. Alexander, can you confirm if
that was the case?
Cheers,
-----BEGIN PGP SIGNATURE-----
iQEcBAEBCAAGBQJQlZvBAAoJEG80Jeu8UPuzmXIH/j1w4BFxPEfkj4nipSurLq/n
3jLExTaGho4ElO82HjAx6hK0BO5aLHKG5A5FrLJaD5oH61xqDMg0vjcbtausLUJs
Pknnf91UtWuyZ3odvcrY0Y7Uv1flQvBri6ZpsmJXCqMQvNh2Uks4+0iNi6vRs8dN
eh3igb6tGt+arOwcUohUo60sivTUPl3KVOSRvZlxAuCzrTGwwJ3B2wDSI2aBI34B
qdfUFB1XcZwalCCbI9opKYnVdQOFrTbypVB0aV38IYkRNLPIbKzvDwHbNTA3N8Fz
wHe3qMiN+De23X19sNvfKHDBZtaz3LFfTnyw4eDkaxocEVscUgeSZxJdhDSBaHg=
=ar5w
-----END PGP SIGNATURE-----
More information about the freebsd-current
mailing list