Bug#557033: linux-image-2.6.31-1-amd64: Kernel logs WARNING at hpet.c:390.

[Gerry Butler <gabutler@acslink.net.au>]

Good morning

> well unless you can't reproduce the message with 2.6.32
> this bug can be closed.

I can neither confirm nor deny that 2.6.32 fixes bug#557033, because I can't boot 2.6.32, and at the moment I can't devote more time to it.

It's clearly a good policy to close bugs that cannot be confirmed to still exist, so I am happy to close it. We can always create a new bug report (or reopen this one) if the bug still exists when 2.6.32 makes it to a stable release. 

Nevertheless, the related bug I entered upstream in bugzilla.kernel.org (14661) seems to be still open. It's been assigned to platform_x86_64@kernel-bugs.osdl.org, but there is no other indication of progress. 

In the meantime, bug#557033 doesn't seem to be having any deleterious effect, except for a message in syslog. 

Regarding my attempt to boot 2.6.32:

When I installed 2.6.31, it installed and booted cleanly, but 2.6.32 didn't. 

> you seem to confuse firmware and drivers.
> and rtl8168d can not be related to booting unless you are netbooting,
> which i kind of doubt.
 
I know that rtl8168d is the Realtek firmware, but nevertheless the apt log used the terminology "driver not available". 

The freeze that occurs early in the boot process for 2.6.32, even before syslog is open, clearly has nothing to do with the Realtek; (as you say, I'm not booting from a network), and probably nothing to do with hpet.c; so that's an entirely different problem.

Thank you for the time you have devoted to it.

Regards

Gerry