From: Marc-Christian Petersen <m.c.p-hi6Y0CQ0nG0@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] ACPI update (20030122)
Date: Fri, 24 Jan 2003 10:09:15 +0100 [thread overview]
Message-ID: <200301241009.15451.m.c.p@gmx.net> (raw)
Hi Dave,
>> I've noticed that with .59 some of my boxes no longer have
>> functioning NICs unless I boot with acpi=off. Packets get
>> transmitted, but nothing ever gets received.
>> Seen this with a 3c509, an 8139, and an e100.
>> Known bug? Fixed in this patch ?
>> Known bug. Not fixed in this patch. Are you sure this is new in recent
>> kernels?
> Only seems to started biting me this last week for some reason.
hehe, I had exactly the same issues starting with 2.4.18 + acpi stuff.
I've noticed that almost every 2nd release broke network cards.
Already reported sometimes.
ciao, Marc
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
next reply other threads:[~2003-01-24 9:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 9:09 Marc-Christian Petersen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-24 1:24 [PATCH] ACPI update (20030122) Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A847137FB7-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-01-24 20:33 ` Marco Walther
2003-01-24 0:09 Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A847137FB5-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-01-24 0:59 ` Dave Jones
2003-01-23 22:44 Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A84725A131-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-01-24 0:00 ` Dave Jones
2003-01-24 0:43 ` Marco Walther
[not found] ` <15920.35870.939062.792709-mWDWuy/8qzhGbVqAl5zy8A@public.gmane.org>
2003-01-26 2:50 ` Sérgio Monteiro Basto
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=200301241009.15451.m.c.p@gmx.net \
--to=m.c.p-hi6y0cq0ng0@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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