Bug#777735: systemd: Disk corruption on reboot initiated through systemd
biebl at debian.org
Fri Feb 13 07:02:09 GMT 2015
Am 13.02.2015 um 07:44 schrieb Michael Biebl:
> I went on and looked what the watchdog package does. Interestingly, it
> clamps any timeout value to 254s, thus not hitting this issue.
> Apparently, i6300esb is able to deal with such a timeout.
> Peter, I therefore recommend you set
> in /etc/systemd/system.conf as well for the time being. This should be
> sufficient to workaround this issue for this buggy driver.
> Setting 256s, does indeed trigger the issue, which leads to the
> conclusion, that the driver is using a char to hold a time value (0-255).
Actually, after a few more experiments, it turns out that for i6300esb,
the safe max value in my qemu VM is 549s. Setting it to 550s triggers
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: OpenPGP digital signature
More information about the Pkg-systemd-maintainers