public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Klaus Zerwes <kzerwes@web.de>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bug ?
Date: Sat, 05 Jan 2002 12:44:21 +0100	[thread overview]
Message-ID: <3C36E715.9030303@web.de> (raw)
In-Reply-To: <3C30A9F0.3070603@web.de> <20011231195115.410b871f.skraw@ithnet.com>

Stephan von Krawczynski wrote:

> On Mon, 31 Dec 2001 19:09:52 +0100
> Klaus Zerwes <kzerwes@web.de> wrote:
> 
> 
>>My PC hangs sporadicaly (every 2 weeks) after heavy Network traffic.
>>I tried to work around the problem by changing the NIC (dmfe > 
>>realtek, using new driver 8139too), but it din't help.
>>
> 
> Hm, I think I saw something the like. The configuration was basically SuSE 7.3
> (with 2.4.10-whatever kernel) and two Realtek cards in a not-trusted cheap box.
> I saw a good amount of collisions on the network, too. I replaced the Realteks
> with DLink and the kernel with 2.4.16 and it did not happen again, although the
> network collisions stayed the same. I tend to think it is the old kernel, but I
> don't like Realtek cards anyway, so I threw them out in one go.
> 
> Tell us if it happens again with 2.4.17, or if you are sure it does not,
> declare it as solved.
> 
> Regards,
> Stephan
> 


I have copmpiles 2.4.16 and did some tests with a mirrored system ( 
only the system, without the harddisks with data) using different 
NICs: Davicom FE (dmfe), RT 8139C (8139too) and SMC 9432 EtherPower II 
  83c172 (epic100).
The System did work fine (the Realtek-NIC I had a huge amount of 
collisions, but it did work!, with the SMC-NIC the Tx-speed was not 
hipeak, but it did work werry constant).
I testet nearly every protocol I can handle and created a realy hard 
networktraffic for a nearly a complete day and the system did not crash!!
Hopefully I was setting my configuration up, connected the 
data-harddisks and rebooted - id did not take 30 minutes and the 
system crashed again. My knowledge of systems is not the best, but for 
me this seems to be a hardwareproblem with the board. From a 
retrospektiv point of view: this box did work for nearly 3 years under 
Linux (suse, debian, slackware) and with FreeBSD and it worked fine - 
but only with one harddisk.
I know that this ALI-board is not the best, but I did not know it is 
realy so bad.

-- 
live free or die :: linux


  reply	other threads:[~2002-01-05 11:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-31 18:09 bug ? Klaus Zerwes
2001-12-31 18:51 ` Stephan von Krawczynski
2002-01-05 11:44   ` Klaus Zerwes [this message]
2002-01-05 15:37     ` Stephan von Krawczynski
2002-01-02 14:03 ` Simon Richter
  -- strict thread matches above, loose matches on Subject: below --
2007-04-01 13:39 Bug? Sascha Curth
2007-04-01 13:54 ` Bug? Michal Piotrowski
2002-05-21  9:48 BUG? alex-n
2002-05-21 10:14 ` BUG? Wilfried Weissmann
2001-12-08  0:31 bug?? wolvie_cobain
2001-12-07 10:33 Bug? Ian Molton
2001-12-07 10:56 ` Bug? DevilKin

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=3C36E715.9030303@web.de \
    --to=kzerwes@web.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skraw@ithnet.com \
    /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