Re: Bug#116780: util-linux: hwclock shouldn't be run

[John Goerzen <jgoerzen@complete.org>]

Daniel Jacobowitz <dan@debian.org> writes:

> John, what kernel/machine do you have hwclock causing a hang?  I'm not
> sure off the top of my head what the status is in 2.2, but 2.4 has a
> "proper" /dev/rtc driver.  We should be using hwclock.  Clock is an
> awful ADB-bit-bashing hack that needs to die.

I'm using BenH's 2.4.x kernels.  I observed this behavior in both
2.4.13pre and 2.4.10 release.  I had not installed hwclock when I was
using any previous version.

Running it causes this:   (from dmesg)

IN from bad port 71 at d983612c
Real Time Clock Driver v1.10e
IN from bad port 71 at d9835eac
IN from bad port 71 at d9835f08
IN from bad port 71 at d9836b64
IN from bad port 71 at d9836bc4
IN from bad port 71 at d9835eac
IN from bad port 71 at d9835f08

The clock program works flawlessly.