FS#56780 - [linux] RTC device not working since kernel 4.13

Attached to Project: Arch Linux
Opened by Arnold (awok) - Tuesday, 19 December 2017, 22:34 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 22 June 2018, 15:50 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan Alexander Steffens (heftig)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:
RTC device is not working on a Dell Inspiron 13 7000 (7352). Running hwclock gives an error and /sys/class/rtc/rtc0/wakealarm does not exist.

Additional info:
Last version it worked on was linux-4.12.13-1, results are the same up to linux-4.14.6-1 (latest as of this report).

sudo hwclock --debug gives:
hwclock from util-linux 2.31
System Time: 1513722780.724086
Trying to open: /dev/rtc0
Trying to open: /dev/rtc
Trying to open: /dev/misc/rtc
No usable clock interface found.
hwclock: Cannot access the Hardware Clock via any known method.

dmesg | grep rtc gives:
[ 0.587068] rtc_cmos 00:01: RTC can wake from S4
[ 0.587078] rtc_cmos: probe of 00:01 failed with error -16
[ 0.602894] hctosys: unable to open rtc device (rtc0)

Steps to reproduce:
1. Install kernel version newer than 4.12.13-1

This task depends upon

Closed by  Doug Newgard (Scimmia)
Friday, 22 June 2018, 15:50 GMT
Reason for closing:  Fixed
Additional comments about closing:  linux 4.17.1-1
Comment by Hubert Toullec (hutou) - Wednesday, 24 January 2018, 17:01 GMT
Same problem on my laptop "HP 15 Notebook", when trying to reinstall Archlinux with iso 2018-01-01.
Comment by loqs (loqs) - Wednesday, 24 January 2018, 17:26 GMT
Can you please bisect the kernel between 4.12 and 4.13 and find the first bad commit and report the issue upstream?
Comment by Alois Nespor (anespor) - Thursday, 12 April 2018, 06:47 GMT
same problem: Toshiba Satellite L-50B, tested 4.16.1-zen and the problem remains
[ 0.406556] hctosys: unable to open rtc device (rtc0)
[ 14.566711] rtc_cmos 00:01: RTC can wake from S4
[ 14.566735] rtc_cmos: probe of 00:01 failed with error -16
[ 15.055796] rtc_cmos 00:01: RTC can wake from S4
[ 15.057045] rtc_cmos: probe of 00:01 failed with error -16
Comment by loqs (loqs) - Friday, 13 April 2018, 23:07 GMT
@anespor unless someone affected works with upstream the issue may remain unfixed indefinitely.
Comment by Arnold (awok) - Friday, 13 April 2018, 23:51 GMT
Sorry, I don't have this machine anymore, so I am unable to provide any more details.

However, it looks like this bug was reported upstream and is being worked on: https://bugzilla.kernel.org/show_bug.cgi?id=199033

Update: I got my laptop back and will be working with upstream on the bug linked above!
Comment by Alois Nespor (anespor) - Sunday, 13 May 2018, 21:49 GMT
Some laptop models will be fixed in the kernel 4.17. https://lkml.org/lkml/2018/4/29/131
You must report specific affected models - see https://bugzilla.kernel.org/show_bug.cgi?id=199033
Comment by Ihor (Ihorko) - Wednesday, 23 May 2018, 08:50 GMT
Hi Jan, Tobias,

could you add patch to 4.16.11 version in order to enable rtc: https://www.spinics.net/lists/linux-acpi/msg82529.html
It should be adopted as base version for this patch is linux-4.17-rc6.

Thanks,
Ihor
Comment by loqs (loqs) - Wednesday, 23 May 2018, 15:20 GMT
@Ihorko the attached patched is the diff after applying a0a37862a4e1844793d39aca9ccb8fecbdcb8659 and the proposed fix please test.
Is upstream targeting the patch for 4.17? Is upstream also going to mark it for stable so it will be backported to the 4.14 and 4.16 series?
Comment by Ihor (Ihorko) - Saturday, 26 May 2018, 07:39 GMT
I've tested patch and it helps me to access hardware clock(/dev/rtc).
There are another ioports-related issues but they are not so needed as rtc.
So please include patch to the next 4.16 series. Because upsteam will not include it earlier then in 4.18 series.
Comment by Alois Nespor (anespor) - Tuesday, 05 June 2018, 09:33 GMT
https://bugzilla.kernel.org/show_bug.cgi?id=199033
please add for kernel 4.17 this patch (source: https://bugzilla.kernel.org/attachment.cgi?id=276097) and you can close this bug.
This patch heading to kernel 4.18.
Thanks!!

Loading...