Bug#487875: marked as done (/dev/rtc is busy)
Your message dated Wed, 25 Jun 2008 03:24:33 +0200
with message-id <20080625012433.GL7212@baikonur.stro.at>
and subject line Re: Bug#487875: /dev/rtc is busy
has caused the Debian Bug report #487875,
regarding /dev/rtc is busy
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
487875: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487875
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.24-1-amd64
Version: 2.6.24-7
For a few months there is no use of hwclock possible
on my computer because of folowing reason:
hwclock --debug
hwclock from util-linux-ng 2.13.1.1
hwclock: Open of /dev/rtc failed, errno=16: Device or resource busy.
No usable clock interface found.
Cannot access the Hardware Clock via any known method.
But I don't know about any program using it.
orca:/proc/driver> cat rtc
rtc_time : 20:19:44
rtc_date : 2008-06-24
rtc_epoch : 1900
alarm : 00:00:00
DST_enable : no
BCD : yes
24hr : yes
square_wave : no
alarm_IRQ : no
update_IRQ : no
periodic_IRQ : no
periodic_freq : 1024
batt_status : okay
Solution: modularizing rtc could help??
--- End Message ---
--- Begin Message ---
Version: 2.6.25-1
On Tue, Jun 24, 2008 at 08:16:59PM +0200, Lars J. Liebschwager wrote:
> Package: linux-image-2.6.24-1-amd64
> Version: 2.6.24-7
>
> For a few months there is no use of hwclock possible
> on my computer because of folowing reason:
>
> >hwclock --debug
>
> hwclock from util-linux-ng 2.13.1.1
> hwclock: Open of /dev/rtc failed, errno=16: Device or resource busy.
> No usable clock interface found.
> Cannot access the Hardware Clock via any known method.
>
> But I don't know about any program using it.
>
> orca:/proc/driver> cat rtc
> rtc_time : 20:19:44
> rtc_date : 2008-06-24
> rtc_epoch : 1900
> alarm : 00:00:00
> DST_enable : no
> BCD : yes
> 24hr : yes
> square_wave : no
> alarm_IRQ : no
> update_IRQ : no
> periodic_IRQ : no
> periodic_freq : 1024
> batt_status : okay
>
> Solution: modularizing rtc could help??
fixed in newer linux images in unstable, thus closing.
thanks for report
--
maks
--- End Message ---
Reply to: