From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964914Ab3GRBQa (ORCPT ); Wed, 17 Jul 2013 21:16:30 -0400 Received: from eu1sys200aog123.obsmtp.com ([207.126.144.155]:54039 "HELO eu1sys200aog123.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1756379Ab3GRBQ3 (ORCPT ); Wed, 17 Jul 2013 21:16:29 -0400 Date: Thu, 18 Jul 2013 13:14:35 +1200 From: Michael Cree To: Richard Henderson Cc: linux-kernel@vger.kernel.org, ink@jurassic.park.msu.ru, mattst88@gmail.com, linux-alpha@vger.kernel.org Subject: Re: [RFC PATCH 00/10] Alpha support for QEMU Message-ID: <20130718011435.GA20007@stolen.phys.waikato.ac.nz> References: <1373996058-13399-1-git-send-email-rth@twiddle.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1373996058-13399-1-git-send-email-rth@twiddle.net> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 16, 2013 at 10:34:08AM -0700, Richard Henderson wrote: > The series seems pretty stable under QEMU, but I have no real hardware > on which to test -- the whole reason I'm interested in QEMU of course. > So I'm hoping that someone will notice this and help me out with testing. Tested the patch series applied against 3.10.1 on a 3-CPU ES45. System came up fine but I noticed date was wrong and had been reset back to the start of the epoch (Jan 1 1970). Appears it is not reading hardware clock correctly on boot. I manually set the clock to the correct time but noticed it is running slow, indeed in a period of 60s the system clock incremented by 21s (+/-1s) so would appear clock is running slow by a factor given by the number of CPUs. Cheers Michael