public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joseph Cheek <joseph@lycoris.com>
To: linux-kernel@vger.kernel.org, acpi-support@lists.sf.net
Subject: 2.4.22: UP+ACPI breaks 8139too [SMP or APM work fine]
Date: Tue, 09 Sep 2003 18:42:00 -0700	[thread overview]
Message-ID: <3F5E8168.9010309@lycoris.com> (raw)

hi all,

until recently i have been running a 2.4 SMP kernel on my UP boxes and 
getting along very well.  but i decided to test a UP kernel, and found 
that i couldn't access the network unless i replaced acpi support with 
apm.  my rtl8139 nic, using the 8139too driver, would give me NETDEV 
WATCHDOG: eth0 timed out over and over in the syslog.

can anyone help me?  i would love to get acpi working again, but i can't 
afford to lose the NIC.

thanks!

joe

-- 
Joseph Cheek, President and CTO, Lycoris
Lycoris Desktop/LX: Familiar.  Powerful.  Open.
joseph@lycoris.com, http://www.lycoris.com/
+1 425 413-9521 voice, +1 425 671-0504 fax



                 reply	other threads:[~2003-09-10  1:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3F5E8168.9010309@lycoris.com \
    --to=joseph@lycoris.com \
    --cc=acpi-support@lists.sf.net \
    --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