linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@debian.org>
To: Torrey Hoffman <thoffman@arnor.net>, gaxt <gaxt@rogers.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux firewire devel <linux1394-devel@lists.sourceforge.net>
Subject: Re: Firewire
Date: Thu, 24 Jul 2003 21:29:08 -0400	[thread overview]
Message-ID: <20030725012908.GT1512@phunnypharm.org> (raw)
In-Reply-To: <20030725012723.GF23196@ruvolo.net>

On Thu, Jul 24, 2003 at 06:27:24PM -0700, Chris Ruvolo wrote:
> On Thu, Jul 24, 2003 at 06:13:37PM -0700, Torrey Hoffman wrote:
> > Sometimes the driver seems to go into an loop of "unsolicted packet
> > received" messages and attempted resets.  Here's what the log looks like
> > when that happens:  (this was on 2.5.75)
> [..]
> > (this sequence repeats until I turn off or unplug the drive.)
> 
> This sounds like what happens to me when I turn on my DV cam.  CPU usage
> goes up to 40% kernel and loops like that until the device goes off.
> 
> What hardware do you have?  lspci?
> 
> Marcello's latest 2.4.22-pre8 updates to rev 1010 of the 1394 modules, so
> I'm curious if I can reproduce this in 2.4 now.

Could both you guys try this workaround? Should prove or disprove my
theory.

Index: linux-2.6/drivers/ieee1394/ohci1394.c
===================================================================
--- linux-2.6/drivers/ieee1394/ohci1394.c	(revision 1013)
+++ linux-2.6/drivers/ieee1394/ohci1394.c	(working copy)
@@ -2366,7 +2366,7 @@
 			ohci1394_stop_context(ohci, d->ctrlClear,
 					      "respTxComplete");
 		else
-			tasklet_schedule(&d->task);
+			dma_trm_tasklet ((unsigned long)d);
 		event &= ~OHCI1394_respTxComplete;
 	}
 	if (event & OHCI1394_RQPkt) {

-- 
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/

  reply	other threads:[~2003-07-25  1:24 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-24 13:34 Firewire gaxt
2003-07-24 22:35 ` Firewire Chris Ruvolo
2003-07-24 22:36   ` Firewire Ben Collins
2003-07-24 23:09     ` Firewire Chris Ruvolo
2003-07-24 23:14       ` Firewire Ben Collins
2003-07-24 23:48         ` Firewire Chris Ruvolo
2003-07-24 23:45           ` Firewire Ben Collins
2003-07-25  0:07             ` Firewire Chris Ruvolo
2003-07-25  0:14           ` Firewire Chris Ruvolo
2003-07-25  1:13       ` Firewire Torrey Hoffman
2003-07-25  1:27         ` Firewire Chris Ruvolo
2003-07-25  1:29           ` Ben Collins [this message]
2003-07-25  2:00             ` Firewire Chris Ruvolo
2003-07-25  2:19               ` Firewire Ben Collins
2003-07-25  3:23             ` Firewire Sam Bromley
2003-07-25  4:12               ` Firewire Ben Collins
2003-07-25  5:39                 ` Firewire Chris Ruvolo
2003-07-25 13:34                   ` Firewire Ben Collins
2003-07-25 14:06                     ` Firewire gaxt
2003-07-25 13:47                       ` Firewire Ben Collins
2003-07-25 14:23                         ` Firewire gaxt
2003-07-25 15:28                           ` Firewire gaxt
2003-07-25 14:29                     ` Firewire Chris Ruvolo
2003-07-25 14:29                       ` Firewire Ben Collins
2003-07-25 15:40                         ` Firewire Ben Collins
2003-07-25 16:07                           ` Firewire Chris Ruvolo
2003-07-25 16:18                             ` Firewire Ben Collins
2003-07-25 17:02                               ` Firewire Chris Ruvolo
2003-07-25 17:07                                 ` Firewire Ben Collins
2003-07-25 17:51                               ` Firewire Torrey Hoffman
2003-07-25 18:13                                 ` Firewire Chris Ruvolo
2003-07-25 18:12                                   ` Firewire Ben Collins
2003-07-25 18:43                                     ` Firewire gaxt
2003-07-25 18:26                                       ` Firewire Ben Collins
2003-07-25 18:45                                         ` Firewire Ben Collins
2003-07-25 19:16                                           ` Firewire gaxt
2003-07-25 19:35                                           ` Firewire Chris Ruvolo
2003-07-25 20:11                                             ` Firewire Ben Collins
2003-07-25 21:48                                               ` Firewire gaxt
2003-07-26  4:41                                               ` Firewire (One fix worked, now getting oops) Sam Bromley
2003-07-26 15:12                                                 ` Ben Collins
2003-07-26 17:41                                                   ` Sam Bromley
2003-07-26 17:45                                                     ` Ben Collins
2003-07-26 16:52                                               ` Firewire Chris Ruvolo
2003-07-26 17:45                                                 ` Firewire Ben Collins
2003-07-25 20:48                                             ` Firewire Torrey Hoffman
2003-07-25 20:44                                               ` Firewire Ben Collins
2003-07-25 18:18                                   ` Firewire Torrey Hoffman
2003-07-25 18:33                                   ` Firewire gaxt
2003-07-25 16:28                           ` Firewire gaxt
2003-07-25 15:53                         ` Firewire Chris Ruvolo
2003-07-25 15:47                           ` Firewire Ben Collins
2003-07-25 16:14                             ` Firewire Chris Ruvolo
2003-07-25 13:34                   ` Firewire Ben Collins

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=20030725012908.GT1512@phunnypharm.org \
    --to=bcollins@debian.org \
    --cc=gaxt@rogers.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=thoffman@arnor.net \
    /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).