Bug 19311

Summary:	6_rc0: kernel: rtc rtc0: invalid alarm value: 2016-9-31 21:39:44
Product:	Mageia	Reporter:	Bit Twister <bittwister2>
Component:	RPM Packages	Assignee:	Kernel and Drivers maintainers <kernel>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, shlomif
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	kernel-4.7.3-1.mga6.src.rpm	CVE:
Status comment:

Description Bit Twister 2016-09-08 09:37:43 CEST

Description of problem:

 kernel: rtc rtc0: invalid alarm value: 2016-9-31 21:39:44

$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-desktop root=LABEL=cauldron noiswmd nokmsboot ipv6.disable=1 audit=0 795


Version-Release number of selected component (if applicable):


How reproducible: ALways


Steps to Reproduce:
1. journalctl | grep 'invalid alarm value'

Comment 1 Marja Van Waes 2016-09-08 11:06:57 CEST

Do you have problems powering off, too?

Wondering because of:

https://lists.debian.org/debian-kernel/2016/04/msg00502.html

CC: (none) => marja11
Assignee: bugsquad => kernel

Comment 2 Bit Twister 2016-09-08 14:08:27 CEST

(In reply to Marja van Waes from comment #1)
> Do you have problems powering off, too?
> 
> Wondering because of:
> 
> https://lists.debian.org/debian-kernel/2016/04/msg00502.html

No, but then again, I do not have an invalid time (1193038:40:16)

Problem was also on the previous kernel release.
Only on this system. 

[root@wb ~]# inxi -C
CPU:       Quad core AMD Athlon II X4 635 (-MCP-) cache: 2048 KB 
           clock speeds: max: 2900 MHz 1: 800 MHz 2: 800 MHz 3

[root@wb ~]# inxi -M
Machine:   System: Hewlett-Packard product: p6610f serial: 4CE03104HY
           Mobo: FOXCONN model: 2AB1 v: DVT
           BIOS: American Megatrends v: 6.02 date: 07/21/2010

Does not happen on my Test Bed node.
[root@tb ~]# inxi -C
CPU:       Dual core AMD Athlon II X2 215 (-MCP-) cache: 1024 KB 
           clock speeds: max: 2700 MHz 1: 2100 MHz 2: 1500 MHz

[root@tb ~]# inxi -M
Machine:   System: LENOVO product: H215 v: IdeaCentre serial: ES06385463
           Mobo: LENOVO model: Tilapia CRB v: INVALID serial: INVALID BIOS: LENOVO v: D2KT21AUS date: 03/12/2010

Source RPM: (none) => kernel-4.7.3-1.mga6.src.rpm

Comment 3 Shlomi Fish 2016-09-08 15:46:10 CEST

Here:

root@telaviv1:~$ journalctl | grep 'invalid alarm value'
root@telaviv1:~$ dmesg | grep 'invalid alarm value'                             
root@telaviv1:~$

(Core i3 x86-64 desktop machine)

I wonder if it happens with a vanilla kernel from kernel.org . Perhaps I should update the kernel-linus package.

CC: (none) => shlomif

Comment 4 Bit Twister 2016-09-08 23:06:47 CEST

(In reply to Shlomi Fish from comment #3)
> Here:
> 
> root@telaviv1:~$ journalctl | grep 'invalid alarm value'
> root@telaviv1:~$ dmesg | grep 'invalid alarm value'                         
> 
> root@telaviv1:~$
> 
> (Core i3 x86-64 desktop machine)
> 
> I wonder if it happens with a vanilla kernel from kernel.org . Perhaps I
> should update the kernel-linus package.

Guessing that will not make a difference since it failed on one and not the other system on my lan.

I just noticed with the latest 35+ kde updates, and 3 reboot test shots, the problem has disappeared. And by coincidence bug 18935 has disappeared again.

I'll mark this resolved and re-open if it shows back up.

Status: NEW => RESOLVED
Resolution: (none) => FIXED