Debian Bug report logs - #627507
Cannot access the Hardware Clock via any known method.

version graph

Package: linux-2.6; Maintainer for linux-2.6 is Debian Kernel Team <debian-kernel@lists.debian.org>;

Reported by: jidanni@jidanni.org

Date: Sat, 21 May 2011 10:45:02 UTC

Severity: normal

Found in version 2.6.38-5

Done: jidanni@jidanni.org

Bug is archived. No further changes may be made.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#627507; Package linux-2.6. (Sat, 21 May 2011 10:45:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to jidanni@jidanni.org:
New Bug report received and forwarded. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Sat, 21 May 2011 10:45:05 GMT) Full text and rfc822 format available.

Message #5 received at submit@bugs.debian.org (full text, mbox):

From: jidanni@jidanni.org
To: submit@bugs.debian.org
Subject: Cannot access the Hardware Clock via any known method.
Date: Sat, 21 May 2011 18:40:38 +0800
Package: linux-2.6
Version: 2.6.38-5

Setting the system clock.
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
Unable to set System Clock to: Sat May 21 10:29:45 UTC 2011 ... ^[[33m(warning).^[[39;49m
^[%@findfs: unable to resolve 'UUID=cfc96b80-b2ec-45b2-90d7-c4b64d4651b6'
Activating swap...done.
Usage: mountpoint [-q] [-d] [-x] path
Checking root file system...fsck from util-linux-ng 2.17.2
/run/rootdev: clean, 166520/492880 files, 1523037/1969962 blocks
done.
Usage: mount -V                 : print version
       mount -h                 : print this help
       mount                    : list mounted filesystems
       mount -l                 : idem, including volume labels
So far the informational part. Next the mounting.
The command is `mount [-t fstype] something somewhere'.
Details found in /etc/fstab may be omitted.
       mount -a [-t|-O] ...     : mount all stuff from /etc/fstab
       mount device             : mount device at the known place
       mount directory          : mount known device here
       mount -t type dev dir    : ordinary mount command
Note that one does not really mount a device, one mounts
a filesystem (of the given type) found on the device.
One can also mount an already visible directory tree elsewhere:
       mount --bind olddir newdir
or move a subtree:
       mount --move olddir newdir
One can change the type of mount containing the directory dir:
       mount --make-shared dir
       mount --make-slave dir
       mount --make-private dir
       mount --make-unbindable dir
One can change the type of all the mounts in a mount subtree
containing the directory dir:
       mount --make-rshared dir
       mount --make-rslave dir
       mount --make-rprivate dir
       mount --make-runbindable dir
A device can be given by name, say /dev/hda1 or /dev/cdrom,
or by label, using  -L label  or by uuid, using  -U uuid .
Other options: [-nfFrsvw] [-o options] [-p passwdfd].
For many more details, say  man 8 mount .
Cleaning up ifupdown....
udevd[47]: failed to create queue file: No such file or directory

udevd[47]: failed to create queue file: No such file or directory

udevd[47]: failed to create queue file: No such file or directory

udevd[47]: failed to create queue file: No such file or directory

Setting the system clock.
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
Unable to set System Clock to: Sat May 21 10:29:45 UTC 2011 ... ^[[33m(warning).^[[39;49m
Loading kernel modules...done.
findfs: unable to resolve 'UUID=cfc96b80-b2ec-45b2-90d7-c4b64d4651b6'
findfs: unable to resolve 'UUID=cfc96b80-b2ec-45b2-90d7-c4b64d4651b6'
findfs: unable to resolve 'UUID=cfc96b80-b2ec-45b2-90d7-c4b64d4651b6'
Activating lvm and md swap...done.
Checking file systems...fsck from util-linux-ng 2.17.2
fsck.ext2: Unable to resolve 'UUID=c914c362-4b46-48be-afaf-6e061825b2ed'
fsck died with exit status 8
^[[31mfailed (code 8).^[[39;49m
File system check failed. A log is being saved in /var/log/fsck/checkfs if that location is writable. Please repair the file system manually. ... ^[[31mfailed!^[[39;49m
A maintenance shell will now be started. CONTROL-D will terminate this shell and resume system boot. ... ^[[33m(warning).^[[39;49m
Give root password for maintenance
(or type Control-D to continue): 
^[[?17;0;64c
^[[01;41;35m18:30 ~#^[[00m lsusb 
unable to initialize libusb: -99
^[[01;41;35m18:30 1 ~#^[[00m reboot
INIT: Switching to runlevel: 6
INIT: Sending processes the TERM signal
error: 'stop-bootlogd-single' exited outside the expected code flow.
Using makefile-style concurrent boot in runlevel 6.
Shutting down ALSA...done (none loaded).
Stopping anac(h)ronistic cron: anacron.
Stopping MTA:.
Stopping deferred execution scheduler: atd.
Stopping resolvconf...done.
Stopping NTP server: ntpd.
Stopping pdnsd.
resolvconf: Error: /etc/resolvconf/run/interface is not a directory
Stopping Network connection manager: wicd.
Stopping HTTP cache proxy server: wwwoffledStopping X font server: xfstt ^[[31mfailed!^[[39;49m
...can't connect to control socket.






Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#627507; Package linux-2.6. (Sat, 21 May 2011 11:00:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Bastian Blank <waldi@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Sat, 21 May 2011 11:00:03 GMT) Full text and rfc822 format available.

Message #10 received at 627507@bugs.debian.org (full text, mbox):

From: Bastian Blank <waldi@debian.org>
To: jidanni@jidanni.org, 627507@bugs.debian.org
Subject: Re: Bug#627507: Cannot access the Hardware Clock via any known method.
Date: Sat, 21 May 2011 12:57:46 +0200
On Sat, May 21, 2011 at 06:40:38PM +0800, jidanni@jidanni.org wrote:
[nothing]

Please specify your problem clearly.

Bastian

-- 
No one may kill a man.  Not for any purpose.  It cannot be condoned.
		-- Kirk, "Spock's Brain", stardate 5431.6




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#627507; Package linux-2.6. (Sat, 21 May 2011 11:12:07 GMT) Full text and rfc822 format available.

Acknowledgement sent to jidanni@jidanni.org:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Sat, 21 May 2011 11:12:07 GMT) Full text and rfc822 format available.

Message #15 received at 627507@bugs.debian.org (full text, mbox):

From: jidanni@jidanni.org
To: waldi@debian.org
Cc: 627507@bugs.debian.org
Subject: Re: Bug#627507: Cannot access the Hardware Clock via any known method.
Date: Sat, 21 May 2011 19:08:08 +0800
>>>>> "BB" == Bastian Blank <waldi@debian.org> writes:
BB> Please specify your problem clearly.

Sorry. All I know is I did this upgrade,
[UPGRADE] acpid 1:2.0.9-1 -> 1:2.0.10-1
[UPGRADE] binutils 2.21.51.20110421-5 -> 2.21.51.20110421-6
[UPGRADE] grub-common 1.99-3 -> 1.99-4
[UPGRADE] grub-pc 1.99-3 -> 1.99-4
[UPGRADE] grub-pc-bin 1.99-3 -> 1.99-4
[UPGRADE] grub2-common 1.99-3 -> 1.99-4
[UPGRADE] initscripts 2.88dsf-13.6 -> 2.88dsf-13.7
[UPGRADE] libfuse2 2.8.4-1.4 -> 2.8.4-1.5
[UPGRADE] libnetaddr-ip-perl 4.042+dfsg-1+b1 -> 4.044+dfsg-1
[UPGRADE] libudev0 168-2 -> 169-1
[UPGRADE] linux-libc-dev 2.6.38-5 -> 2.6.39-1
[UPGRADE] perl 5.12.3-6 -> 5.12.3-7
[UPGRADE] perl-base 5.12.3-6 -> 5.12.3-7
[UPGRADE] perl-doc 5.12.3-6 -> 5.12.3-7
[UPGRADE] perl-modules 5.12.3-6 -> 5.12.3-7
[UPGRADE] sysv-rc 2.88dsf-13.6 -> 2.88dsf-13.7
[UPGRADE] sysvinit 2.88dsf-13.6 -> 2.88dsf-13.7
[UPGRADE] sysvinit-utils 2.88dsf-13.6 -> 2.88dsf-13.7
[UPGRADE] udev 168-2 -> 169-1
then rebooted and got those messages. The workaround was to reboot a
second time with 2.6.37-2-686 instead of 2.6.38-2-686, which made none
of those messages.




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#627507; Package linux-2.6. (Sat, 21 May 2011 11:48:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Jonathan Nieder <jrnieder@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Sat, 21 May 2011 11:48:04 GMT) Full text and rfc822 format available.

Message #20 received at 627507@bugs.debian.org (full text, mbox):

From: Jonathan Nieder <jrnieder@gmail.com>
To: jidanni@jidanni.org
Cc: 627507@bugs.debian.org
Subject: Re: Cannot access the Hardware Clock via any known method.
Date: Sat, 21 May 2011 06:45:14 -0500
jidanni@jidanni.org wrote:

> Sorry. All I know is I did this upgrade,

[... packages that are not linux-image-foo ...]

> then rebooted and got those messages. The workaround was to reboot a
> second time with 2.6.37-2-686 instead of 2.6.38-2-686, which made none
> of those messages.

To be clear, does that mean you had been running 2.6.38-5 before the
upgrade, too?




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#627507; Package linux-2.6. (Sat, 21 May 2011 11:57:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to jidanni@jidanni.org:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Sat, 21 May 2011 11:57:04 GMT) Full text and rfc822 format available.

Message #25 received at 627507@bugs.debian.org (full text, mbox):

From: jidanni@jidanni.org
To: jrnieder@gmail.com
Cc: 627507@bugs.debian.org
Subject: Re: Cannot access the Hardware Clock via any known method.
Date: Sat, 21 May 2011 19:55:22 +0800
>>>>> "JN" == Jonathan Nieder <jrnieder@gmail.com> writes:
JN> To be clear, does that mean you had been running 2.6.38-5 before the
JN> upgrade, too?
Yes. But I was forced to reboot with my backup,
$ apt-show-versions|grep linux-image
linux-image-2.6-686/unstable uptodate 2.6.38+34
linux-image-2.6.37-2-686 2.6.37-2 installed: No available version in archive
linux-image-2.6.38-2-686/unstable uptodate 2.6.38-5
linux-image-686/unstable uptodate 2.6.38+34
if I wanted to boot successfully.




Reply sent to jidanni@jidanni.org:
You have taken responsibility. (Mon, 23 May 2011 01:48:06 GMT) Full text and rfc822 format available.

Notification sent to jidanni@jidanni.org:
Bug acknowledged by developer. (Mon, 23 May 2011 01:48:06 GMT) Full text and rfc822 format available.

Message #30 received at 627507-done@bugs.debian.org (full text, mbox):

From: jidanni@jidanni.org
To: 627507-done@bugs.debian.org
Subject: seems an apt-get upgrade fixed it
Date: Mon, 23 May 2011 09:45:30 +0800
Seems an apt-get upgrade fixed it. Closing.
See you tomorrow for sure though.




Bug archived. Request was from Debbugs Internal Request <owner@bugs.debian.org> to internal_control@bugs.debian.org. (Mon, 20 Jun 2011 07:28:20 GMT) Full text and rfc822 format available.

Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Wed Apr 16 16:43:52 2014; Machine Name: buxtehude.debian.org

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.