From: Stephan von Krawczynski <skraw@ithnet.com>
To: "David B. Stevens" <dsteven3@maine.rr.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [patch] O(1) scheduler, -H7
Date: Sun, 13 Jan 2002 20:08:15 +0100 [thread overview]
Message-ID: <20020113200815.28b14e54.skraw@ithnet.com> (raw)
In-Reply-To: <3C41DA53.D91FE6E2@maine.rr.com>
In-Reply-To: <20020113185732.72ea3aa8.skraw@ithnet.com> <Pine.LNX.4.33.0201132056360.8784-100000@localhost.localdomain> <20020113194958.62f8f674.skraw@ithnet.com> <3C41DA53.D91FE6E2@maine.rr.com>
On Sun, 13 Jan 2002 14:04:51 -0500
"David B. Stevens" <dsteven3@maine.rr.com> wrote:
> It works fine on top of 2.4.18-pre3 in UP config.
Sorry, I should have attached a short summary of my system:
dual PIII-1GHz / board Asus CUV4X-D (via chipset, no I did not encounter any
problems so far) / 2 GB RAM with highmem support on"Network" refers to tulip
quad-card in this case. It really hangs in _every_ boot at the same operation
(a ping).
Regards,
Stephan
> This e-maile is from such a system.
>
> Cheers,
> Dave
>
> Stephan von Krawczynski wrote:
> >
> > On Sun, 13 Jan 2002 20:58:12 +0100 (CET)
> > Ingo Molnar <mingo@elte.hu> wrote:
> >
> > >
> > > On Sun, 13 Jan 2002, Stephan von Krawczynski wrote:
> > >
> > > > sched.o sched.c sched.c:21: asm/sched.h: No such file or directory
> > >
> > > Please re-download the 2.4.17 -H7 patch, i've fixed this.
> >
> > Ok, I tried on top of vanilla 2.4.17 and it works.
> >
> > Seems like 2.4.18-pre3 and H7 don't like each other :-)
> >
> > Regards,
> > Stephan
prev parent reply other threads:[~2002-01-13 19:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-13 19:34 [patch] O(1) scheduler, -H7 Ingo Molnar
2002-01-13 17:57 ` Stephan von Krawczynski
2002-01-13 19:58 ` Ingo Molnar
2002-01-13 18:20 ` Stephan von Krawczynski
2002-01-13 18:49 ` Stephan von Krawczynski
2002-01-13 19:04 ` David B. Stevens
2002-01-13 19:08 ` Stephan von Krawczynski [this message]
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=20020113200815.28b14e54.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=dsteven3@maine.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.