linux-kernel - Re: hwclock problems still present in 2.6.27-rc4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080821165648.GA2732@x200.localdomain>
Date:	Thu, 21 Aug 2008 20:56:48 +0400
From:	adobriyan@...il.com
To:	Norbert Preining <preining@...ic.at>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: hwclock problems still present in 2.6.27-rc4

On Thu, Aug 21, 2008 at 06:39:20PM +0200, Norbert Preining wrote:
> I have read through quite some threads on lkml and bug reports regarding
> the hangs/freezes of the kernel when hwclock is called.
> 
> I still see that behaviour on 2.6.27-rc4 with
> CONFIG_HPET_TIMER=y
> CONFIG_HPET_EMULATE_RTC=y
> CONFIG_HPET=y
> CONFIG_HPET_MMAP=y
> CONFIG_RTC_LIB=y
> CONFIG_RTC_CLASS=y
> CONFIG_RTC_HCTOSYS=y
> CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
> CONFIG_RTC_INTF_SYSFS=y
> CONFIG_RTC_INTF_PROC=y
> CONFIG_RTC_INTF_DEV=y
> CONFIG_RTC_DRV_CMOS=y
> (all rtc and hpet related config vars).

> What is the recommended way to fix that, or do you need some more
> information?

Remove CONFIG_RTC_* options for start. Unless you knowingly selected
them, of course.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/