From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Michael Guntsche <mike-Z92qn3yYq0hWk0Htik3J/w@public.gmane.org>
Cc: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Network failures with ACPI enabled (kernel 2.4, 2.6) PROBLEM FOUND!!!!!!
Date: Sat, 3 Jan 2004 22:06:22 +0100 [thread overview]
Message-ID: <20040103210622.GA2775@elf.ucw.cz> (raw)
In-Reply-To: <20031231172328.5ae00921.mike-Z92qn3yYq0hWk0Htik3J/w@public.gmane.org>
Hi!
> > The fact that transmit works and receive fails is a clue.
> > Probably the broadcom uses interrupts for receive, but doesn't
> > use interrupts for transmit. So if it were not getting interrupts,
> > transmit could still send frames.
> >
> > So if you enable the parallel port in ECP mode, broadcom works --
> > but if the port is disabled, or enabled but not in ECP mode, it fails?
>
> Hmm I played around with it some more. If I lower the speed on my
> notebook
> to 10baseT-HD the transfer works at 800KB/s.
> But errors and frames on the device (eth0) are increasing at an alarming
> rate.
> For me it looks like that the problem occurs if the network card gets a
> lot of inbound traffic.
Is not this plain old "ACPI stays to log with interrupts disabled"?
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
next prev parent reply other threads:[~2004-01-03 21:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 22:36 Network failures with ACPI enabled (kernel 2.4, 2.6) PROBLEM FOUND!!!!!! Brown, Len
[not found] ` <BF1FE1855350A0479097B3A0D2A80EE0CC8954-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2003-12-30 23:17 ` Michael Guntsche
[not found] ` <20031231001716.76cb2e8d.mike-Z92qn3yYq0hWk0Htik3J/w@public.gmane.org>
2003-12-30 23:46 ` Michael Guntsche
[not found] ` <20031231004648.531549af.mike-Z92qn3yYq0hWk0Htik3J/w@public.gmane.org>
2003-12-31 6:21 ` Len Brown
[not found] ` <1072851661.2363.228.camel-D2Zvc0uNKG8@public.gmane.org>
2003-12-31 16:23 ` Michael Guntsche
[not found] ` <20031231172328.5ae00921.mike-Z92qn3yYq0hWk0Htik3J/w@public.gmane.org>
2004-01-03 21:06 ` Pavel Machek [this message]
2003-12-31 23:02 ` Nate Lawson
-- strict thread matches above, loose matches on Subject: below --
2003-12-30 21:17 Brown, Len
[not found] ` <BF1FE1855350A0479097B3A0D2A80EE0CC8953-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2003-12-30 22:22 ` Michael Guntsche
2003-12-31 23:46 ` Nate Lawson
2003-12-30 0:08 Network failures with ACPI enabled (kernel 2.4, 2.6) Michael Guntsche
2003-12-30 15:57 ` Michael Guntsche
2003-12-30 17:48 ` Len Brown
2003-12-30 18:23 ` Michael Guntsche
[not found] ` <20031230192301.5d17d418.mike-Z92qn3yYq0hWk0Htik3J/w@public.gmane.org>
2003-12-30 20:45 ` Network failures with ACPI enabled (kernel 2.4, 2.6) PROBLEM FOUND!!!!!! Michael Guntsche
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=20040103210622.GA2775@elf.ucw.cz \
--to=pavel-+zi9xunit7i@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=mike-Z92qn3yYq0hWk0Htik3J/w@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