All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Boler <j.m.boler@sms.ed.ac.uk>
To: Werner Almesberger <werner@almesberger.net>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: [uml-user] hack: avoid "Registered protocol family 2" hang
Date: Fri, 05 Mar 2004 13:56:47 +0000	[thread overview]
Message-ID: <4048871F.4080400@sms.ed.ac.uk> (raw)
In-Reply-To: <20040305100144.E26293@almesberger.net>

[-- Attachment #1: Type: text/plain, Size: 472 bytes --]

Werner Almesberger wrote:
> I've attached a little hack that should make the hang after
> NET: Registered protocol family 2
> disappear. This isn't the real solution (haven't yet figured
> out how this is truly supposed to work on non-SMP), but it 
> gives me a happier UML :-)
> 
> - Werner
> 

The actual bug has been fixed. The problem was the host cpu Hz was being 
truncated to a signed int so uml wouldn't run on a host faster than 2.1Ghz.

Patch attached

Jonathan

[-- Attachment #2: hz.patch --]
[-- Type: text/plain, Size: 470 bytes --]

--- arch/um/kernel/time.c       2004-03-05 13:54:12.262248632 +0000
+++ ../../linux-2.6.3/arch/um/kernel/time.c     2004-03-04 08:54:33.000000000 +0000
@@ -88,7 +88,8 @@
 static unsigned long long get_host_hz(void)
 {
        char mhzline[16], *end;
-       int ret, mult, mhz, rest, len;
+       int ret, mult, rest, len;
+       unsigned long long mhz;
 
        ret = cpu_feature("cpu MHz", mhzline, 
                          sizeof(mhzline) / sizeof(mhzline[0]));


  reply	other threads:[~2004-03-05 14:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-05 13:01 [uml-devel] hack: avoid "Registered protocol family 2" hang Werner Almesberger
2004-03-05 13:56 ` Jonathan Boler [this message]
2004-03-08 13:55   ` [uml-devel] Re: [uml-user] " Werner Almesberger

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=4048871F.4080400@sms.ed.ac.uk \
    --to=j.m.boler@sms.ed.ac.uk \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    --cc=werner@almesberger.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.