Marking fixed release based on comment #14
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1410604
Title:
ISST-LTE: unable to open
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1410604
Title:
ISST-LTE: unable to open rtc d
Indeed the code in
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/rtc/hctosys.c
looks like it runs entirely "self-"triggered (late_initcall), not
triggered by an userspace call. This function tries to open the device
which simply isn't present (yet) at that time. So may
Booting with "debug=y" works better, as then the initramfs debug goes
right on the console, instead of /run/initramfs/initramfs.debug. This
shows that even the initrd starts after the error message, so this must
come from the kernel itself:
Loading Linux 4.4.0-8-generic ...
Loading initial ramdisk
Thanks for the journal. This shows that the error message happens way
earlier than userspace/pid 1 starts. So it's either the kernel itself,
or the initramfs. I can indeed see this error message in our ppc64el
scalingstack instances as well.
So I went through the initramfs-tools hooks and scripts
Log from booting with "debug", i. e. set -x output from initramfs.
** Attachment added: "initramfs debug log"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1410604/+attachment/4586567/+files/initramfs.debug
--
You received this bug notification because you are a member of Ub
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 a
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin1604
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1410604
Title:
ISST-LTE: unable to open rtc device
To manage notificat
Hi Canonical,
Even thought this is a benign error, it is seen on all archs on every
release as far back as trusty (at least). Can you please set a target
for resolution? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
** Tags added: vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1410604
Title:
ISST-LTE: unable to open rtc device
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu
Setting to package "init" on LP side, as it appears to be an init issue
rather than a kernel issue.
** Package changed: ubuntu => init-system-helpers (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
12 matches
Mail list logo
