Daniel Kahn Gillmor wrote: > Another use of bug reports (especially ones about bugs that make > machines unbootable, and would therefore be critical) is to keep > packages from filtering down into testing while they're in a dangerous > state. Package maintainers file RC bugs to prevent this kind of thing if an isue comes to their attention outside the bts. Or just fix the bug in unstable, as I've done.. > Wow, thanks! I think you hit the nail on the head. hwclock --show > drives the CPU to 100% kernel. > > When i remove the rtc-dev module, hwclock --show fails, but at least > it returns immediately. > > The next time i'm physically near the machine, i'll try reseating the > battery to clear it up, and report back if that clears my problem. I suspect that this will happen to anyone who buys a slug, never configures the clock using the standard firmware, and immediatly installs Debian. What I was told when this happened to me last year is that the standard firmware has some magic that starts the clock running when it's configured. If a Debian install is done straightaway, that never happens.. Reseating the battery solved the problem for me. -- see shy jo
Attachment:
signature.asc
Description: Digital signature