From: "David S. Miller" <davem@davemloft.net>
To: Kai Makisara <Kai.Makisara@kolumbus.fi>
Cc: netdev@oss.sgi.com, ganesh.venkatesan@intel.com
Subject: Re: e1000 lockup in linux 2.6.9-rc2
Date: Mon, 20 Sep 2004 13:56:06 -0700 [thread overview]
Message-ID: <20040920135606.7a0885df.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0409202339050.2170@kai.makisara.local>
On Mon, 20 Sep 2004 23:53:15 +0300 (EEST)
Kai Makisara <Kai.Makisara@kolumbus.fi> wrote:
> When I started large data transfers in 100 Mb/s network, my computer very
> soon locked totally (i.e., not responding to network, keyboard and mouse
> dead). This had not happened for several days with 2.6.9-rc2 when the
> network activity had been light (1 Mb/s DSL).
>
> Some experimentation showed that the lockups were caused by this patch
> fragment in 2.6.9-rc2:
Please make sure you have this patch in your
tree, it should fix your problem:
# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
# 2004/09/13 12:58:04-07:00 ak@muc.de
# [NET]: Fix missing spin lock in lltx path.
#
# This fixes a silly missing spin lock in the relock path. For some
# reason it seems to still work when you don't have spinlock debugging
# enabled.
#
# Please apply.
#
# Thanks to Arjan's spinlock debug kernel for finding it.
#
# Signed-off-by: Andi Kleen <ak@muc.de>
# Signed-off-by: David S. Miller <davem@davemloft.net>
#
# net/sched/sch_generic.c
# 2004/09/13 12:57:46-07:00 ak@muc.de +3 -1
# [NET]: Fix missing spin lock in lltx path.
#
# This fixes a silly missing spin lock in the relock path. For some
# reason it seems to still work when you don't have spinlock debugging
# enabled.
#
# Please apply.
#
# Thanks to Arjan's spinlock debug kernel for finding it.
#
# Signed-off-by: Andi Kleen <ak@muc.de>
# Signed-off-by: David S. Miller <davem@davemloft.net>
#
diff -Nru a/net/sched/sch_generic.c b/net/sched/sch_generic.c
--- a/net/sched/sch_generic.c 2004-09-20 13:36:19 -07:00
+++ b/net/sched/sch_generic.c 2004-09-20 13:36:19 -07:00
@@ -148,8 +148,10 @@
spin_lock(&dev->queue_lock);
return -1;
}
- if (ret == NETDEV_TX_LOCKED && nolock)
+ if (ret == NETDEV_TX_LOCKED && nolock) {
+ spin_lock(&dev->queue_lock);
goto collision;
+ }
}
/* NETDEV_TX_BUSY - we need to requeue */
next prev parent reply other threads:[~2004-09-20 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 20:53 e1000 lockup in linux 2.6.9-rc2 Kai Makisara
2004-09-20 20:56 ` David S. Miller [this message]
2004-09-20 21:25 ` Kai Makisara
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=20040920135606.7a0885df.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Kai.Makisara@kolumbus.fi \
--cc=ganesh.venkatesan@intel.com \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).