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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 21 Jan 2011 11:23:22 +0100
From:	Andreas Schwab <schwab@...ux-m68k.org>
To:	John Stultz <john.stultz@...aro.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Alessandro Zummo <a.zummo@...ertech.it>,
	Thomas Gleixner <tglx@...utronix.de>,
	Richard Cochran <richardcochran@...il.com>
Subject: Re: [PATCH 3/5] RTC: Rework RTC code to use timerlist for events

John Stultz <john.stultz@...aro.org> writes:

> On Thu, 2011-01-20 at 19:07 +0100, Andreas Schwab wrote:
>> John Stultz <john.stultz@...aro.org> writes:
>> 
>> > This patch reworks a large portion of the generic RTC code
>> > to in-effect virtualize the rtc interrupt code.
>> 
>> That breaks RTC on powermac which uses rtc-generic.
>> 
>> # hwclock 
>> select() to /dev/rtc0 to wait for clock tick timed out
>
> Actually, can you also send strace output?

ioctl(4, RTC_UIE_ON, 0)                 = 0
select(5, [4], NULL, NULL, {5, 0})      = 0 (Timeout)
write(2, "select() to /dev/rtc0 to wait fo"..., 55) = 55
ioctl(4, RTC_UIE_OFF, 0)                = 0

CONFIG_RTC_INTF_DEV_UIE_EMUL was never enabled, and RTC_UIE_ON returned
EINVAL before, which caused hwclock to fall back to polling.

Andreas.

-- 
Andreas Schwab, schwab@...ux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ