From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Peter Daum <gator@cs.tu-berlin.de>
Cc: peter_daum@t-online.de (Peter Daum), <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.22 with CONFIG_M686: networking broken
Date: Thu, 4 Sep 2003 11:20:57 +0200 [thread overview]
Message-ID: <200309041120.57233.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <Pine.LNX.4.30.0309031227100.10173-100000@swamp.bayern.net>
AFAIR local APIC is enabled by default for CONFIG_M686
and it is not for CONFIG_MPENTIUM4.
If you are using local APIC please try with "noapic" boot option
or recompile kernel without local APIC support.
This is just a guess...
--bartlomiej
On Wednesday 03 of September 2003 13:08, Peter Daum wrote:
> Hi,
>
> It seems, like kernel version 2.4.22 introduced some weird bug,
> that causes all kinds of network malfunctions, when the kernel is
> compiled with "CONFIG_M686".
>
> I am sorry, that I can't come up with a clearer error
> description, but the whole issue is pretty mysterious: there is
> no actual error occurring, but some networking functionality is so
> slow that it's for all practical purposes useless. The best test
> cases I could find are:
>
> - getting a file via ftp (e.g. wget ftp://...): Data rate over a
> normally fast network connection is ~ 200 bytes /second, the
> connection soon dies with a timeout
>
> - writing to a SMB share (provided, that samba is running on the
> machine) is awfully slow and eventually aborted (Windows
> complains about "network congestion")
> reading via SMB works as usual ...
>
> I upgraded the kernel on a bunch of machines - on most of them, I
> had to immediately go back to the previous kernel because there
> were obvious problems; some machines, however, worked perfectly
> normal with the new kernel.
>
> I tried lots of different options until I eventually found out,
> that the single setting that makes all the difference is the
> processor type: Independently of any other settings, all kernels
> with "CONFIG_M686" exhibit these problems; when I change this to
> "CONFIG_MPENTIUM4" and recompile, everything seems to work.
>
> (By the way: the affected machines have "Pentium Pro" or "Pentium
> II" processors - is it safe to run a kernel compiled for "Pentium
> IV" on such boxes?)
>
> Regards,
> Peter Daum
next prev parent reply other threads:[~2003-09-04 9:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 11:08 Peter Daum
2003-09-03 11:48 ` Matthias Andree
2003-09-04 9:20 ` Bartlomiej Zolnierkiewicz [this message]
2003-09-04 16:32 ` Peter Daum
2003-09-07 15:14 ` Adrian Bunk
2003-09-07 18:38 ` Peter Daum
2003-09-07 19:42 ` Adrian Bunk
2003-12-09 22:47 Peter Daum
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=200309041120.57233.bzolnier@elka.pw.edu.pl \
--to=b.zolnierkiewicz@elka.pw.edu.pl \
--cc=gator@cs.tu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peter_daum@t-online.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®