[arch-general] Bizarre Clock Reset 8/1 -> 9/1 after apcupsd shutdown??

[Leonid Isaev]

On Wed, 01 Aug 2012 14:56:20 -0500
"David C. Rankin" <drankinatty at suddenlinkmail.com> wrote:

> Guys,
> 
>    This is one for you to puzzle over. I've never seen it before. I had an 
> apcupsd commanded shutdown at Aug  1 13:20:15 (not uncommon - power is 
> terrible). However, when I restarted the hwclock had magically jumped ahead
> by 1 full month to Sept. 1. (the box was down for 56 minutes until I
> returned from lunch)
> 
>    Then on restart, I was dropped into the maintenance shell and required to 
> run fsck manually due to the future date. There was a message that stated 
> something line "run fsck manually on /dev/sdc5 ... the system will reboot 
> automatically after fsck completes" (this looked like an abbreviated 
> maintenance shell -- I guess due to the fact that the root fs was the one
> that was being checked /dev/sdc5.
> 
>    fsck completed (e2fsck), but the box didn't reboot. So I typed 'reboot'
> -- nothing happened. Checked /usr/bin and reboot was present. So then I
> finally did ctrl+alt+del and the box restarted. I was then dumped into the
> normal maintenance shell to fsck /home on /dev/sdc7. It completed and reboot
> worked normally.
> 
>    My questions are (1) does anybody have any idea how this can happen? (2) 
> Anybody else every seen this? and (3) could the kernel apcupsd segfault
> (shown below) be the cause?
> 
>    Any ideas welcome. Strange stuff...
> 
>    The relevant everything.log snippet and bios info is below:
> 
> Aug  1 13:20:15 providence apcupsd[3477]: apcupsd shutdown succeeded
> Aug  1 13:20:15 providence kernel: [171092.364247] apcupsd[3477]: segfault
> at 0 ip 0805c706 sp bfcdfff0 error 4 in apcupsd[8048000+38000]

Does apcupsd routinely segfault?

> Aug  1 13:20:15 providence ntpd[3454]: Listen normally on 6 eth0
> 192.168.7.124 UDP 123
> Aug  1 13:20:15 providence ntpd[3454]: peers refreshed
> Aug  1 13:20:15 providence ntpd[3454]: new interface(s) found: waking up
> resolver Aug  1 13:20:15 providence postfix/postfix-script[13735]: stopping
> the Postfix mail system
> Aug  1 13:20:15 providence postfix/master[3868]: terminating on signal 15
> Aug  1 13:20:15 providence postfix/postfix-script[13738]: waiting for the 
> Postfix mail system to terminate
> Aug  1 13:20:16 providence dhcpcd[424]: eth0: sending IPv6 Router
> Solicitation Aug  1 13:20:19 providence ntpd[3454]: ntpd exiting on signal 15

Your NTP behaves strangely... why would it refresh timeservers and then
shutdown at the same timestamp? It looks like your ntp did something funny and
incorrectly adjusted the HW clock.

> Aug  1 13:20:19 providence dhcpcd[13884]: sending signal 1 to pid 424
> Aug  1 13:20:19 providence dhcpcd[424]: received SIGHUP, releasing
> Aug  1 13:20:19 providence dhcpcd[424]: eth0: releasing lease of
> 192.168.7.124 Aug  1 13:20:19 providence dhcpcd[13884]: waiting for pid 424
> to exit Aug  1 13:20:19 providence dhcpcd[424]: eth0: removing interface
> Aug  1 13:20:19 providence kernel: [171096.790000] pcieport 0000:00:1c.0: 
> wake-up capability enabled by ACPI
> Aug  1 13:20:19 providence syslog-ng[352]: syslog-ng shutting down; 
> version='3.3.5'
> Sep  1 14:16:20 providence kernel: [    0.000000] Initializing cgroup subsys 
> cpuset
> Sep  1 14:16:20 providence kernel: [    0.000000] Initializing cgroup subsys
> cpu Sep  1 14:16:20 providence kernel: [    0.000000] Linux version
> 3.4.7-1-ARCH (tobias at T-POWA-LX) (gcc version 4.7.1 20120721 (prerelease)
> (GCC) ) #1 SMP PREEMPT Sun Jul 29 20:05:01 UTC 2012
> 
> BIOS Information
>          Vendor: Dell Inc.
>          Version: A04
>          Release Date: 02/09/2005
> 
> 



-- 
Leonid Isaev
GnuPG key: 0x164B5A6D
Fingerprint: C0DF 20D0 C075 C3F1 E1BE  775A A7AE F6CB 164B 5A6D
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://mailman.archlinux.org/pipermail/arch-general/attachments/20120801/812673ba/attachment.asc>