[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#475959: marked as done (hpet=force vs /dev/rtc)



Your message dated Tue, 20 May 2008 18:57:42 +0200
with message-id <20080520165742.GC13383@stro.at>
and subject line Re: hpet=force vs /dev/rtc
has caused the Debian Bug report #475959,
regarding hpet=force vs /dev/rtc
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.)


-- 
475959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475959
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.24-1-686
Version: 2.6.24-5
Severity: important

If I boot with hpet=force I avoid approximately 35 wakeups per second.
Unfortunately I noticed two unnecessary delays during the boot process.
These are caused by the fact that hwclock is not able to read the time
from /dev/rtc. The hwclock command works only with --directisa.

I installed hardy with vmlinuz-2.6.24-16-generic in another partition on
the same machine. There are no problems with hpet=force and hwclock.
Ubuntu uses CONFIG_HPET_EMULATE_RTC=y.

Is there any reason why this option is not set in the Debian kernel?

-- 
Psst! Geheimtipp: Online Games kostenlos spielen bei den GMX Free Games! 
http://games.entertainment.gmx.net/de/entertainment/games/free



--- End Message ---
--- Begin Message ---
Version: 2.6.25-1

> CONFIG_HPET_EMULATE_RTC=y
> is set in Package: linux-image-2.6.25-1-686
> and hwlock works fine (as expected)!


-- 
maks


--- End Message ---

Reply to: