netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>,
	netdev@vger.kernel.org, Kyle Lucke <klucke@us.ibm.com>,
	Raghavendra Koushik <raghavendra.koushik@neterion.com>,
	Al Viro <viro@ftp.linux.org.uk>
Subject: Re: [BUG] RTNL and flush_scheduled_work deadlocks
Date: Thu, 15 Feb 2007 10:58:13 -0800	[thread overview]
Message-ID: <45D4AD45.3010503@candelatech.com> (raw)
In-Reply-To: <20070214235420.GA13816@electric-eye.fr.zoreil.com>

Francois Romieu wrote:
> Ben Greear <greearb@candelatech.com> :
> [...]
>> I seem to be able to trigger this within about 1 minute on a
>> particular 2.6.18.2 system with some 8139too devices, so if someone
>> has a patch that could be tested, I'll gladly test it.  For
>> whatever reason, I haven't hit this problem on 2.6.20 yet, but
>> that could easily be dumb luck, and I haven't been running .20
>> very much.
> 
> Bandaid below. It is not complete if your device hits the tx_watchdog
> hard but it should help.

So far, I've been running several hours without problems, so
this does appear to be helping.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2007-02-15 18:59 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14 21:27 [BUG] RTNL and flush_scheduled_work deadlocks Stephen Hemminger
2007-02-14 21:44 ` Ben Greear
2007-02-14 23:54   ` Francois Romieu
2007-02-15 18:58     ` Ben Greear [this message]
2007-02-15 22:37 ` [PATCH 1/4] r8169: RTNL and flush_scheduled_work deadlock Francois Romieu
2007-02-20 16:18   ` Jeff Garzik
2007-02-15 22:37 ` [PATCH 2/4] sis190: " Francois Romieu
2007-02-15 22:37 ` [PATCH 3/4] 8139too: " Francois Romieu
2007-02-16  7:59   ` Jarek Poplawski
2007-02-16 20:20     ` Francois Romieu
2007-02-16 20:36       ` Stephen Hemminger
2007-02-17 20:54         ` Francois Romieu
2007-02-19 12:05       ` Jarek Poplawski
2007-02-19 21:08         ` Francois Romieu
2007-04-04 23:38   ` Ben Greear
2007-04-05 11:17     ` Francois Romieu
2007-02-15 22:37 ` [PATCH 4/4] s2io: " Francois Romieu
2007-02-16  7:29 ` [BUG] RTNL and flush_scheduled_work deadlocks Jarek Poplawski
2007-02-16  7:40   ` Ben Greear
2007-02-16  8:10     ` Jarek Poplawski
2007-02-16  8:23       ` Ben Greear
2007-02-16  9:04         ` Jarek Poplawski
2007-02-16 12:12           ` Jarek Poplawski
2007-02-16 16:06             ` Ben Greear
2007-02-20  8:23               ` Jarek Poplawski
2007-02-16 18:31     ` Stephen Hemminger
2007-02-16 19:04       ` Ben Greear
2007-02-19  6:13         ` [PATCH 1/2] " Jarek Poplawski
2007-02-19  6:27           ` Ben Greear
2007-02-19  7:11             ` Jarek Poplawski
2007-02-19  7:40               ` Jarek Poplawski
2007-03-05  8:36             ` [PATCH v.2] " Jarek Poplawski
2007-02-19  6:55         ` [PATCH 2/2] " Jarek Poplawski
2007-02-19  7:18           ` Jarek Poplawski

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=45D4AD45.3010503@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=klucke@us.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=raghavendra.koushik@neterion.com \
    --cc=romieu@fr.zoreil.com \
    --cc=shemminger@linux-foundation.org \
    --cc=viro@ftp.linux.org.uk \
    /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).