From: Nick Craig-Wood <ncw1@axis.demon.co.uk>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] [PATCH] - fix for 2.4.22-7um RTC on CPUs faster than 2.1 GHz
Date: Fri, 19 Dec 2003 11:37:57 +0000 [thread overview]
Message-ID: <20031219113757.GA22923@axis.demon.co.uk> (raw)
In-Reply-To: <000901c3c53e$4a759550$0201a8c0@hawk>
On Thu, Dec 18, 2003 at 02:09:39AM -0600, Christopher S. Aker wrote:
> Enabling the RTC in 2.4.22-7um produced a hang very soon after INIT at boot time.
>
> I discovered host_hz as an int overflows past 2.1 Ghz (2147483647
> hz).
Ah, I've been wondering why I couldn't get 2.4.22-7um to work - this
fixes it for me!
BTW the patch appeared to be whitespace mangled - I had to apply it
with patch --ignore-whitespace
Thanks
Nick
--
Nick Craig-Wood
ncw1@axis.demon.co.uk
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2003-12-19 11:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 7:24 [uml-devel] uml-patch-2.4.22-7 without CONFIG_MODE_TT failed Jeff Chua
2003-12-18 8:09 ` [uml-devel] [PATCH] - fix for 2.4.22-7um RTC on CPUs faster than 2.1 GHz Christopher S. Aker
2003-12-18 18:30 ` Jeff Dike
2003-12-18 20:39 ` Matt Ayres
2003-12-18 21:52 ` Jeff Dike
2003-12-19 11:37 ` Nick Craig-Wood [this message]
2003-12-18 19:21 ` [uml-devel] uml-patch-2.4.22-7 without CONFIG_MODE_TT failed Jeff Dike
2003-12-18 19:50 ` BlaisorBlade
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031219113757.GA22923@axis.demon.co.uk \
--to=ncw1@axis.demon.co.uk \
--cc=caker@theshore.net \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.