All of lore.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: 48+ 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 --
2024-08-08 15:41 bug? Yusuf said Çolak
2024-08-08 17:27 ` bug? Daniel P. Berrangé
2019-08-05  2:42 BUG, Su Yanjun
2016-07-24 13:46 Bug: "git log --format='format:%+s%+b'" doesn't insert newline before body Ilya Tumaykin
2016-07-25  6:55 ` Bug: Beat Bolli
2016-07-06 14:02 Bug? Wjatscheslaw Stoljarski
2016-07-07  6:55 ` Bug? Sascha Hauer
2016-07-07  9:37   ` Bug? Wjatscheslaw Stoljarski
2016-07-07 10:07     ` Bug? Sascha Hauer
2015-04-10 18:27 Bug? Barclay Jameson
2014-04-21 16:16 Bug: "corrupt leaf. slot offset bad": root subvolume unmountable, "btrfs check" crashes Andreas Reis
2014-04-21 19:13 ` Andreas Reis
2014-04-22 18:16   ` Andreas Reis
2014-04-23  2:55     ` Duncan
2014-04-25  2:04       ` Bug: Andreas Reis
2014-02-17 10:28 bug? Dirk Winning, junidas GmbH
2014-02-17 14:51 ` bug? Pasi Kärkkäinen
2013-11-20 22:18 BUG?? Bruno Bruzzano
2013-11-21 12:02 ` BUG?? Luiz Augusto von Dentz
2013-11-21 14:07   ` BUG?? Bruno Bruzzano
2013-11-21 14:17     ` BUG?? Bruno Bruzzano
     [not found] <8E0A14A4C9B95B459AE214584119C1EB3BC909B3@Hal.ad.unb.ca>
2013-01-28 16:37 ` bug? Mathieu Desnoyers
2013-01-23 20:09 bug? Yang Wang
2012-11-23 10:32 Bug? Dirk Winning
2012-11-23 16:46 ` Bug? George Dunlap
2012-04-21 12:53 bug? Thomas Weber
2012-04-24 15:26 ` bug? Josef Bacik
2012-04-24 15:47   ` bug? Thomas Weber
2011-11-23  9:18 Bug? Kormos 'Morc' Gábor
2012-03-22 11:07 ` Bug? Kormos 'Morc' Gábor
2010-02-26 11:15 Bug ;( Ян Программист
2009-08-12 22:07 bug: Dennis Gilmore
2008-08-23 16:17 BUG? Mateyko
2008-08-25 21:35 ` BUG? Luis R. Rodriguez
2007-04-01 13:39 Bug? Sascha Curth
2007-04-01 13:54 ` Bug? Michal Piotrowski
2005-05-19  6:25 bug? Holub Zoltan
2005-05-19  6:25 ` bug? Rudolf Marek
2003-10-08 18:08 BUG ? :) =?unknown-8bit?q?Jos=E9?= Mans
2003-10-08 19:07 ` Alex Zarochentsev
2003-07-17 23:40 Bug? WebExplode.com
2003-06-30 10:15 Bug? Hrvoje Habjanic
2003-03-17 14:06 bug ? Andreas Westin
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 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.