public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Raphael_Manfredi@pobox.com (Raphael Manfredi)
To: linux-kernel@vger.kernel.org
Subject: Re: 8139too on ABIT BP6 causes "eth0: transmit timed out"
Date: 29 Oct 2001 13:43:12 GMT	[thread overview]
Message-ID: <9rjmdg$i2$1@lyon.ram.loc> (raw)
In-Reply-To: <16095.1004308212@nice.ram.loc> <039901c1600b$b33fe3a0$0201a8c0@HOMER>
In-Reply-To: <039901c1600b$b33fe3a0$0201a8c0@HOMER>

Quoting Martin Eriksson <nitrax@giron.wox.org> from ml.linux.kernel:
:What Bios are you running? You should be running the modified RU1.25 Bios,
:and have enabled MPS 1.4. Also disable "Spread Spectrum" and do *not*
:overclock.

I have the RU BIOS, I enabled MPS 1.4.
What is "Spread Spectrum?".
I don't overclock.  I never do.

I remember seeing messages about network lockups on the ABIT BP6, and
there was a patch submitted to the list.  It had to do with a Sysreq patch
that would "do something to the APIC" and re-enable network interrupts.

However, I don't remember who this was, and where the patch is.

Is the older Becker driver for the RTL8139 more robust?  I know it's no longer
maintained, but if I want to try it, how do I proceed?  I don't remember
seeing it offered in the configuration menu.

Raphael

      parent reply	other threads:[~2001-10-29 13:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-28 22:30 8139too on ABIT BP6 causes "eth0: transmit timed out" Raphael Manfredi
2001-10-28 23:11 ` APM disable broken (was -> Re: 8139too on ABIT BP6 causes "eth0: transmit timed out" ) erich
2001-10-29  0:12   ` victor
2001-10-29  2:43   ` Oden Eriksson
2001-10-29  5:32 ` 8139too on ABIT BP6 causes "eth0: transmit timed out" Daniel R. Warner
     [not found] ` <039901c1600b$b33fe3a0$0201a8c0@HOMER>
2001-10-29 13:43   ` Raphael Manfredi [this message]

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='9rjmdg$i2$1@lyon.ram.loc' \
    --to=raphael_manfredi@pobox.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