hwclock --systohc locks machine up, RTC conflict problems

From: kinesis
Date: Sun Dec 09 2007 - 19:51:26 EST



Issuing the command hwclock --systohc and sometimes at boot --hctosys causes
my machine to freeze.

The reason is there is a problem loading rtc-cmos. I will say that my
machine also runs Windows, and it detects the device fine as a Real Time
Clock/CMOS driver at io range 0070-0071. According to /proc/ioports rtc is
probed at 0070-0077.

During boot we get the following when attempting to modprobe rtc-cmos:


root@excalibur:/usr/src/linux-2.6# dmesg|grep rtc

drivers/rtc/hctosys.c: unable to open rtc device (rtc0)

rtc_cmos 00:09: i/o registers already in use

rtc_cmos: probe of 00:09 failed with error -16

root@excalibur:/usr/src/linux-2.6#



this has happened with the stock kernel that came with my distribution, as
well.

Apparently you can only use 0070-0071 for my rtc? how can I get the device
to work?

here is /proc/interrupts:

CPU0 CPU1
0: 23106 13272660 IO-APIC-edge timer
1: 49 5781 IO-APIC-edge i8042
8: 0 1 IO-APIC-edge rtc
9: 159 9301 IO-APIC-fasteoi acpi
12: 1818 190257 IO-APIC-edge i8042
14: 0 35 IO-APIC-edge ide0
17: 2174 312677 IO-APIC-fasteoi nvidia
18: 363 27432 IO-APIC-fasteoi HDA Intel
19: 1914 283347 IO-APIC-fasteoi ndiswrapper
20: 6434 1328206 IO-APIC-fasteoi eth0
21: 0 0 IO-APIC-fasteoi ohci_hcd:usb2
22: 0 0 IO-APIC-fasteoi ehci_hcd:usb1
23: 209 19944 IO-APIC-fasteoi sata_nv
NMI: 0 0 Non-maskable interrupts
LOC: 13272488 22989 Local timer interrupts
RES: 105913 91197 Rescheduling interrupts
CAL: 151 134 function call interrupts
TLB: 18445 19521 TLB shootdowns
TRM: 0 0 Thermal event interrupts
THR: 0 0 Threshold APIC interrupts
SPU: 0 0 Spurious interrupts
ERR: 0


--
View this message in context: http://www.nabble.com/hwclock---systohc-locks-machine-up%2C-RTC-conflict-problems-tp14245613p14245613.html
Sent from the linux-kernel mailing list archive at Nabble.com.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/