problems with hwclock on arm (avila board with ixdp425) | |
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] | |
Problem -
hwclock is not working on the boards, I have.
At --debug flag, it hangs at "/dev/rtc does not have interrupt
functions. Waiting in loop for time from /dev/rtc to change"
strace on hwclock showed that it loops at RTC_RD_TIME ioctl.
Am I missing some patches or am I missing some configuration?
How can I rectify the problem?
Environment -
GW Avila boards (GW2348-4)
Linux 2.6.18
Debian distribution
IXDP425
util-linux-2.12p
------------------------------------------------------------------------
-----------------
root:~# ls -al /dev/rtc*
lrwxrwxrwx 1 root root 4 Mar 30 2007 /dev/rtc -> rtc0
crw-r--r-- 1 root root 254, 0 Mar 30 2007 /dev/rtc0
root:~#
------------------------------------------------------------------------
-----------------
.config contents -
1292 #
1293 # Real Time Clock
1294 #
1295 CONFIG_RTC_LIB=y
1296 CONFIG_RTC_CLASS=y
1297 CONFIG_RTC_HCTOSYS=y
1298 CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
1299
1300 #
1301 # RTC interfaces
1302 #
1303 CONFIG_RTC_INTF_SYSFS=y
1304 CONFIG_RTC_INTF_PROC=y
1305 CONFIG_RTC_INTF_DEV=y
1306 # CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
1307
1308 #
1309 # RTC drivers
1310 #
1311 CONFIG_RTC_DRV_X1205=y
1312 CONFIG_RTC_DRV_DS1307=y
1313 # CONFIG_RTC_DRV_DS1553 is not set
1314 # CONFIG_RTC_DRV_ISL1208 is not set
1315 CONFIG_RTC_DRV_DS1672=y
1316 # CONFIG_RTC_DRV_DS1742 is not set
1317 CONFIG_RTC_DRV_PCF8563=y
1318 # CONFIG_RTC_DRV_PCF8583 is not set
1319 # CONFIG_RTC_DRV_RS5C372 is not set
1320 # CONFIG_RTC_DRV_M48T86 is not set
1321 # CONFIG_RTC_DRV_TEST is not set
1322 # CONFIG_RTC_DRV_V3020 is not set
1323
1324 #
------------------------------------------------------------------------
-----------------
root:~# hwclock --show --debug
hwclock from util-linux-2.12p
Using /dev/rtc interface to clock.
Last drift adjustment done at 293368709 seconds after 1969
Last calibration done at 293368709 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
/dev/rtc does not have interrupt functions. Waiting in loop for time
from /dev/rtc to change
------------------------------------------------------------------------
--------------------
strace on hwclock - (command run: strace hwclock --show)
execve("/sbin/hwclock", ["hwclock", "--show"], [/* 16 vars */]) = 0
uname({sys="Linux", node="root", ...}) = 0
brk(0) = 0x17000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.preload", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=5575, ...}) = 0
old_mmap(NULL, 5575, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40015000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/lib/libc.so.6", O_RDONLY) = 3
read(3, "\177ELF\1\1\1a\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\350[\1\000"...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1159708, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0x40017000
old_mmap(NULL, 1196844, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) =
0x4001d000
old_mmap(0x40135000, 40960, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED,
3, 0x110000) = 0x40135000
old_mmap(0x4013f000, 9004, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x4013f000
close(3) = 0
munmap(0x40015000, 5575) = 0
gettimeofday({2906605805, 710000}, NULL) = 0
brk(0) = 0x17000
brk(0x38000) = 0x38000
brk(0) = 0x38000
getuid32() = 0
open("/dev/rtc", O_RDONLY|O_LARGEFILE) = 3
close(3) = 0
stat64("/etc/adjtime", {st_mode=S_IFREG|0644, st_size=44, ...}) = 0
open("/etc/adjtime", O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=44, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0x40015000
read(3, "0.000000 1103000000 0.000000\n110"..., 4096) = 44
close(3) = 0
munmap(0x40015000, 4096) = 0
open("/dev/rtc", O_RDONLY|O_LARGEFILE) = 3
ioctl(3, RTC_UIE_ON, 0) = -1 ENOTTY (Inappropriate ioctl
for device)
ioctl(3, RTC_RD_TIME, {tm_sec=36, tm_min=13, tm_hour=5, tm_mday=8,
tm_mon=1, tm_year=162, ...}) = 0
ioctl(3, RTC_RD_TIME, {tm_sec=36, tm_min=13, tm_hour=5, tm_mday=8,
tm_mon=1, tm_year=162, ...}) = 0
ioctl(3, RTC_RD_TIME, {tm_sec=36, tm_min=13, tm_hour=5, tm_mday=8,
tm_mon=1, tm_year=162, ...}) = 0
ioctl(3, RTC_RD_TIME, {tm_sec=36, tm_min=13, tm_hour=5, tm_mday=8,
tm_mon=1, tm_year=162, ...}) = 0
ioctl(3, RTC_RD_TIME, {tm_sec=36, tm_min=13, tm_hour=5, tm_mday=8,
tm_mon=1, tm_year=162, ...}) = 0
ioctl(3, RTC_RD_TIME, {tm_sec=36, tm_min=13, tm_hour=5, tm_mday=8,
tm_mon=1, tm_year=162, ...}) = 0
ioctl(3, RTC_RD_TIME, {tm_sec=36, tm_min=13, tm_hour=5, tm_mday=8,
tm_mon=1, tm_year=162, ...}) = 0
ioctl(3, RTC_RD_TIME, {tm_sec=36, tm_min=13, tm_hour=5, tm_mday=8,
tm_mon=1, tm_year=162, ...}) = 0
ioctl(3, RTC_RD_TIME, {tm_sec=36, tm_min=13, tm_hour=5, tm_mday=8,
tm_mon=1, tm_year=162, ...}) = 0
ioctl(3, RTC_RD_TIME, {tm_sec=36, tm_min=13, tm_hour=5, tm_mday=8,
tm_mon=1, tm_year=162, ...}) = 0
ioctl(3, RTC_RD_TIME, {tm_sec=36, tm_min=13, tm_hour=5, tm_mday=8,
tm_mon=1, tm_year=162, ...}) = 0
ioctl(3, RTC_RD_TIME, {tm_sec=36, tm_min=13, tm_hour=5, tm_mday=8,
tm_mon=1, tm_year=162, ...}) = 0
ioctl(3, RTC_RD_TIME, {tm_sec=36, tm_min=13, tm_hour=5, tm_mday=8,
tm_mon=1, tm_year=162, ...}) = 0
ioctl(3, RTC_RD_TIME, {tm_sec=36, tm_min=13, tm_hour=5, tm_mday=8,
tm_mon=1, tm_year=162, ...}) = 0
ioctl(3, RTC_RD_TIME, {tm_sec=36, tm_min=13, tm_hour=5, tm_mday=8,
tm_mon=1, tm_year=162, ...}) = 0
ioctl(3, RTC_RD_TIME, {tm_sec=36, tm_min=13, tm_hour=5, tm_mday=8,
tm_mon=1, tm_year=162, ...}) = 0
<< keeps going in loop >>
Thanks in advance.
with rgds,
Bhanu Prakash A
The information contained in, or attached to, this e-mail, contains confidential information and is intended solely for the use of the individual or entity to whom they are addressed and is subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email.
www.aztecsoft.com
-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
FAQ: http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette: http://www.arm.linux.org.uk/mailinglists/etiquette.php
[Site Home] [IETF Annouce] [Security] [Bugtraq] [Linux] [Linux ARM Kernel] [Linux MIPS] [ECOS] [Tools] [DDR & Rambus] [Monitors]