* hwclock --systohc locks machine up, RTC conflict problems
@ 2007-12-10 0:51 kinesis
2007-12-19 0:31 ` Ingo Molnar
0 siblings, 1 reply; 2+ messages in thread
From: kinesis @ 2007-12-10 0:51 UTC (permalink / raw)
To: linux-kernel
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: hwclock --systohc locks machine up, RTC conflict problems
2007-12-10 0:51 hwclock --systohc locks machine up, RTC conflict problems kinesis
@ 2007-12-19 0:31 ` Ingo Molnar
0 siblings, 0 replies; 2+ messages in thread
From: Ingo Molnar @ 2007-12-19 0:31 UTC (permalink / raw)
To: kinesis; +Cc: linux-kernel, Thomas Gleixner, H. Peter Anvin
* kinesis <jriley1337@yahoo.com> wrote:
> my machine is 64bit running SLAMD64 v12 (slackware) Linux excalibur
> 2.6.24-rc4-kinesis-g94545bad #8 SMP Sun Dec 9 10:47:29 PST 2007 x86_64
> x86_64 x86_64 GNU/Linux
>
> Issuing the command hwclock --systohc and sometimes at boot --hctosys
> causes my machine to freeze.
could you try the "x86: IO delay quirk" patch attached to this bugzilla:
http://bugzilla.kernel.org/show_bug.cgi?id=6307
please boot with io_delay=0xed [or io_delay=udelay or io_delay=none].
does that fix the lockups?
Ingo
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-12-19 0:31 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-12-10 0:51 hwclock --systohc locks machine up, RTC conflict problems kinesis
2007-12-19 0:31 ` Ingo Molnar
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).