public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felix Maibaum <f.maibaum@tu-bs.de>
To: linux <linux-kernel@vger.kernel.org>
Subject: 2.4.0 bug in SHM an via-rhine or is it my fault?
Date: Tue, 09 Jan 2001 14:50:06 +0100	[thread overview]
Message-ID: <3A5B170E.F48872A@tu-bs.de> (raw)

Hi folks!

I searched the kernel archives for information on this at least half a
yearback but I found only one article on the subject and that was never
replied to:

I'm using a via-rhine chip (DFE-530TX) on a 10 Mbit network, I use 2.4.0
final, Athlon (classic) 1Gig, Abit-KA7 mobo (via KX133), Debian woody.
whenever I try to get a file on my local network, meaning I get close to
the 10Mbit barrier the network card hangs up. Traffic just stops.
One ifdown/ifup and everything works fine again. (for about 10 seconds)
this problem has persisted for some time now, I thought it would be
fixed in the final, but, alas, it hasn't. It only happens during high
traffic, too, at about 400k, no problem!


Something new that cropped up in prerelease:

My SHM stopped working!
everything was fine in test12, and after that all I got was "no space
left on device".
Has anything changed that one should know about? I mounted shm like it's
written in the help, and on a friends celeron SMP machine it works fine,
I just don't know what I did wrong.

any ideas on any of the 2 problems?

TIA

Felix Maibaum


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2001-01-09 13:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-09 13:50 Felix Maibaum [this message]
2001-01-09 14:01 ` 2.4.0 bug in SHM an via-rhine or is it my fault? Nils Philippsen
2001-01-09 14:12   ` Felix Maibaum
2001-01-09 19:30 ` Adrian Chung
2001-01-10 12:36   ` Adrian Chung

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=3A5B170E.F48872A@tu-bs.de \
    --to=f.maibaum@tu-bs.de \
    --cc=linux-kernel@vger.kernel.org \
    /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