public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Tyler Longren" <tyler@captainjack.com>
To: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: 2.4.x, smp, eepro100
Date: Fri, 5 Oct 2001 14:01:52 -0500	[thread overview]
Message-ID: <001e01c14dd0$326264d0$2a23b1cf@win2k> (raw)

Hello everyone,

I've been having major troubles with a machine here.  Here's my setup:

OS: Slackware 8.0
Kernel: 2.4.5_nosmp, 2.4.5, and 2.4.10
NIC: eepro100

Anyway, installed Slackware with the default scsi kernel.  Everything worked
fine.  I re-compiled 2.4.5 to enable smp support.  After re-compiling
everything is stable until a few hundred megs gets uploaded to the box.
After a few hundred megs get upped to the box (through ftp), eth0 just dies.
The same thing happened in 2.4.9 and now also happens in 2.4.10.  There's
some odd messages coming from dmesg:
eth0:        8   0000a022.
eth0:        9   0000a020.
eth0:        10 0000a020.
eth0:        11 0000a020.
eth0:        12 0000a022.
eth0:        13 0000a022.
eth0:        14 0000a020.
eth0:        15 0000a020.
eth0:        16 0000a020.
eth0:        17 00000001.
eth0:        18 00000001.

I have no idea why this is happening.  My ethernet card uses the eepro100
module.  When I re-compile the kernel, I use the default config file for
slackware (so it should be like the default Slackware scsi kernel).  The
only thing I do is add SMP support.

Any ideas anyone?

Thanks,
Tyler Longren



             reply	other threads:[~2001-10-05 19:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-05 19:01 Tyler Longren [this message]
2001-10-09 16:58 ` 2.4.x, smp, eepro100 java programmer
  -- strict thread matches above, loose matches on Subject: below --
2001-10-05 19:27 Jesse Pollard

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='001e01c14dd0$326264d0$2a23b1cf@win2k' \
    --to=tyler@captainjack.com \
    --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