From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: twaugh@redhat.com
Subject: Re: [BUG] 2.4.18-pre/rc broke PLIP
Date: Thu, 07 Mar 2002 06:47:51 +0300 [thread overview]
Message-ID: <3C86E2E7.3080300@yahoo.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
Hello.
Tim Waugh wrote:
> Does 2.4.19-pre2 not work for you?
I had the similar problem with plip at 2.4.18
and 2.4.19-pre2 seems to fix it for me (though
I have seen a comments that it doesn't work for
others).
But I had another problem with plip for years,
which was not fixed by 2.4.19-pre2:
if I do `ifdown plip0` and then `ifup plip0`,
plip no longer works and the kernel logs timeouts,
just like in 2.4.18.
To work around the problem I removed "DISABLE(dev-irq);"
from plip_close(), and it works nice since.
So, if you are already on this, could you please
look at the attached "patch" and make a real fix
(if this is not the one already)?
[-- Attachment #2: plip.diff --]
[-- Type: text/plain, Size: 514 bytes --]
--- linux/drivers/net/plip.c Sun Sep 30 23:26:07 2001
+++ linux/drivers/net/plip.c Thu Mar 7 02:47:43 2002
@@ -163,7 +163,7 @@
static int plip_ioctl(struct net_device *dev, struct ifreq *ifr, int cmd);
static int plip_preempt(void *handle);
static void plip_wakeup(void *handle);
-\f
+
enum plip_connection_state {
PLIP_CN_NONE=0,
PLIP_CN_RECEIVE,
@@ -1177,7 +1177,6 @@
struct plip_local *rcv = &nl->rcv_data;
netif_stop_queue (dev);
- DISABLE(dev->irq);
synchronize_irq();
if (dev->irq == -1)
next reply other threads:[~2002-03-07 3:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-07 3:47 Stas Sergeev [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-24 23:20 [BUG] 2.4.18-pre/rc broke PLIP Mikael Pettersson
2002-03-05 16:36 ` Bill Davidsen
2002-03-05 16:55 ` Tim Waugh
2002-03-05 21:20 ` Bill Davidsen
2002-03-05 22:04 ` Tim Waugh
2002-03-06 19:08 ` Bill Davidsen
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=3C86E2E7.3080300@yahoo.com \
--to=stssppnn@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stas.orel@mailcity.com \
--cc=twaugh@redhat.com \
/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