touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #132179
[Bug 1410604] Re: ISST-LTE: unable to open rtc device
The only place known to me that does that is /etc/init.d/hwclock.sh,
which is from util-linux. Something similar is also done under upstart
from /etc/init/hwclock.conf where hwclock is called with --systz. This
quite plausibly opens rtc as well.
However, these two scripts aren't being run at all any more under
systemd -- there it would be timedated which accesses /dev/rtc, but I
don't see how this is being activated that early (it usually doesn't run
at boot at all).
Can you please confirm whether this happens under upstart or systemd? In
the latter case, can you please do
sudo journalctl -b > /tmp/journal.txt
and attach /tmp/journal.txt here? Thanks!
** Package changed: init-system-helpers (Ubuntu) => util-linux (Ubuntu)
** Changed in: util-linux (Ubuntu)
Status: New => Incomplete
** Changed in: util-linux (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1410604
Title:
ISST-LTE: unable to open rtc device
Status in util-linux package in Ubuntu:
Incomplete
Bug description:
== Comment: #0 - Chanh H. Nguyen <chnguyen@xxxxxxxxxx> - 2015-01-09 17:30:08 ==
We use DVD to install Ubuntu 15.04 kernel 3.18.0-8-generic version on our PowerVM system. After install, I am seeing this error "/build/buildd/linux-3.18.0/drivers/rtc/hctosys.c: unable to open rtc device" on the dmesg log...
root@pole1lp3:~# uname -a
Linux pole1lp3 3.18.0-8-generic #9-Ubuntu SMP Mon Jan 5 22:52:15 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
root@pole1lp3:~# dmesg |grep rtc
[ 0.556763] /build/buildd/linux-3.18.0/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 3.296241] rtc-generic rtc-generic: rtc core: registered rtc-generic as rtc0
root@pole1lp3:~#
== Comment: #2 - David Heller <hellerda@xxxxxxxxxx> - 2015-01-13 20:53:50 ==
It must be an order of operations thing: something is trying to do the hctosys before the driver is loaded. A few seconds later the driver loads and it seems fine after that.
root@pole1lp3:~# dmesg | grep rtc
[ 0.551202] /build/buildd/linux-3.18.0/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 3.353719] rtc-generic rtc-generic: rtc core: registered rtc-generic as rtc0
root@pole1lp3:~# find /dev -name \*rtc\*
/dev/rtc
/dev/rtc0
root@pole1lp3:~# hwclock
Tue 13 Jan 2015 07:36:15 PM CST -0.779773 seconds
root@pole1lp3:~# hwclock --hctosys
root@pole1lp3:~# date
Tue Jan 13 19:38:05 CST 2015
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1410604/+subscriptions