mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: victor <ixnay@infonegocio.com>
To: erich@uruk.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: APM disable broken (was -> Re: 8139too on ABIT BP6 causes "eth0: transmit timed out" )
Date: Mon, 29 Oct 2001 01:12:58 +0100	[thread overview]
Message-ID: <1871217837878.20011029011258@infonegocio.com> (raw)
In-Reply-To: <E15xz5T-0008SA-00@trillium-hollow.org>
In-Reply-To: <E15xz5T-0008SA-00@trillium-hollow.org>

Hello erich,

Monday, October 29, 2001, 12:11:27 AM, you wrote:

i have a dual celeron in a bp6, i reflash de bios with
http://bp6.gamesquad.net/bios.phtml the bios revision
Final RU BIOS (newest Fianl Release BIOS from Abit)
and i have a ovislink 8139C chip and a hp 100mb switch and all works
fine


euo> Raphael Manfredi <Raphael_Manfredi@pobox.com> wrote:

euo> ...[recent 2.4-based kernel]...

>> but this problem is not specific to that kernel.  I've been having
>> it for a looong time.
>> 
>> Specifically, I get:
>> 
>>  NETDEV WATCHDOG: eth0: transmit timed out
euo> ...
>> and then the machine is dead, network-wise.  I have to reboot (reset).
>> 
>> Note that I am on an ABIT BP6 board, and I do get a lot of APIC errors
>> under heavy network traffic, which is what raises the above.
>> By heavy network traffic, I mean a 7 Mb/s full duplex (it's a 100 Mb/s
>> LAN).

euo> I had what looks like exactly this problem with my ABIT BP6 -based machine
euo> running RH 7.1, and the problem turned out to be the interaction between
euo> SMP and the APM BIOS, when APM is turned on.  A different network card,
euo> but the same symptom.  Another symptom I would occasionally see was a
euo> certain kind of hard-disk hang, but only on the integrated HPT366
euo> controller.

euo> I suggest you try either:

euo>   --  adding the "noapic" line to your kernel command-line (which will
euo>       lose you some I/O performance since normal interrupts will not be
euo>       handled APIC-style)
euo>   --  completely disabling APM from your kernel configuration.  Using
euo>       "apm=off/disabled" (I can't remember the exact one you're supposed
euo>       to use here) does not totally disable APM usage.


euo> This brings me to my other point.  During the Linux kernel startup
euo> code (in the early assembly), the APM BIOS checking code leaves the
euo> BIOS in the "connected" state even if the kernel option for disabling
euo> APM or the SMP forced disable of APM is triggered.

euo> This makes various motherboards (such as the ABIT BP6) unstable.

euo> The Right Thing to do would be to disconnect the APM BIOS if it is
euo> determined that APM support should be disabled.

euo> I could probably generate a patch to fix this if it looked like it would
euo> be accepted by the folks maintaining APM support...

euo> --
euo>     Erich Stefan Boleyn     <erich@uruk.org>     http://www.uruk.org/
euo> "Reality is truly stranger than fiction; Probably why fiction is so popular"
euo> -
euo> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
euo> the body of a message to majordomo@vger.kernel.org
euo> More majordomo info at  http://vger.kernel.org/majordomo-info.html
euo> Please read the FAQ at  http://www.tux.org/lkml/



-- 
Best regards,
 victor                            mailto:ixnay@infonegocio.com


  reply	other threads:[~2001-10-29  0:13 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 [this message]
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

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=1871217837878.20011029011258@infonegocio.com \
    --to=ixnay@infonegocio.com \
    --cc=erich@uruk.org \
    --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

all inboxes | Powered by JetHome®