* Re: 2.4.22 with CONFIG_M686: networking broken
@ 2003-12-09 22:47 Peter Daum
2003-12-10 14:13 ` [Linux-ATM-General] " chas williams
0 siblings, 1 reply; 3+ messages in thread
From: Peter Daum @ 2003-12-09 22:47 UTC (permalink / raw)
To: linux-kernel; +Cc: linux-atm-general
Hi,
... the same bug is still present in kernel version 2.4.23.
As I know meanwhile, it only occurs on ATM/LANE network connections.
For more details about the problem, see the threads on
"2.4.22 with CONFIG_M686: networking broken"
http://testing.lkml.org/slashdot.php?mid=330251
and
"[2.4 patch] fix CONFIG_X86_L1_CACHE_SHIFT"
http://testing.lkml.org/slashdot.php?mid=331650
Regards,
Peter Daum
In article <Pine.LNX.4.30.0309031227100.10173-100000@swamp.bayern.net> I
wrote:
> 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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Linux-ATM-General] Re: 2.4.22 with CONFIG_M686: networking broken
2003-12-09 22:47 2.4.22 with CONFIG_M686: networking broken Peter Daum
@ 2003-12-10 14:13 ` chas williams
2003-12-10 15:50 ` Peter Daum
0 siblings, 1 reply; 3+ messages in thread
From: chas williams @ 2003-12-10 14:13 UTC (permalink / raw)
To: Peter Daum; +Cc: linux-kernel, linux-atm-general
In message <Pine.LNX.4.30.0312092344360.17719-100000@swamp.bayern.net>,Peter Da
um writes:
>... the same bug is still present in kernel version 2.4.23.
>As I know meanwhile, it only occurs on ATM/LANE network connections.
which atm card are you using? if you are using a he155/622 then i am
probably setting the cacheline size wrong.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Linux-ATM-General] Re: 2.4.22 with CONFIG_M686: networking broken
2003-12-10 14:13 ` [Linux-ATM-General] " chas williams
@ 2003-12-10 15:50 ` Peter Daum
0 siblings, 0 replies; 3+ messages in thread
From: Peter Daum @ 2003-12-10 15:50 UTC (permalink / raw)
To: chas williams; +Cc: linux-kernel, linux-atm-general
On Wed, 10 Dec 2003, chas williams wrote:
> In message <Pine.LNX.4.30.0312092344360.17719-100000@swamp.bayern.net>,Peter Da
> um writes:
> >... the same bug is still present in kernel version 2.4.23.
> >As I know meanwhile, it only occurs on ATM/LANE network connections.
>
> which atm card are you using? if you are using a he155/622 then i am
> probably setting the cacheline size wrong.
>
It is a Marconi/Nicstar Forerunner LE 155 (IDT77211 rev. 3)
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-12-10 15:53 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-12-09 22:47 2.4.22 with CONFIG_M686: networking broken Peter Daum
2003-12-10 14:13 ` [Linux-ATM-General] " chas williams
2003-12-10 15:50 ` Peter Daum
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).