From: Ben Greear <greearb@candelatech.com>
To: netdev@oss.sgi.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Tulip (DFE-570tx) & keyboard lockup in 2.6.9 and other 2.6 kernels.
Date: Thu, 24 Feb 2005 16:16:33 -0800 [thread overview]
Message-ID: <421E6E61.3040005@candelatech.com> (raw)
In-Reply-To: <421CF0BA.1020100@candelatech.com>
Ben Greear wrote:
> I finally had some time to debug this one a little more
> thoroughly. On two different machines (Shuttle SB61G1) I
> get the same results, so I do not believe it is bad hardware...
>
> The bug is as follows:
>
> I have 1 4-port tulip NIC in the machine. If I generate traffic
> between two interfaces, it runs fine. But, if I start running traffic
> on all 4 interfaces, the keyboard quits taking input, and ethernet
> traffic stops on at least a few of the interfaces. I can still ssh
> into the machine (via the rtl8139 interface), so at least one of the
> processors (I'm using SMP on an P4 HT processor) is working. I also
> enabled NMI and that does not trigger.
This was my bug. I was holding a lock that was required for receiving a packet
while calling the hard_start_xmit method. When an IRQ happened while I was in
the hard_start_xmit method, the IRQ could not grab the lock, and just sat there
spinning...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2005-02-25 0:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 21:08 Tulip (DFE-570tx) & keyboard lockup in 2.6.9 and other 2.6 kernels Ben Greear
2005-02-25 0:16 ` Ben Greear [this message]
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=421E6E61.3040005@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--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).