From: Chris Ruvolo <chris+lkml@ruvolo.net>
To: Ben Collins <bcollins@debian.org>
Cc: Sam Bromley <sbromley@cogeco.ca>,
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: Fri, 25 Jul 2003 10:02:55 -0700 [thread overview]
Message-ID: <20030725170255.GN23196@ruvolo.net> (raw)
In-Reply-To: <20030725161803.GJ1512@phunnypharm.org>
[-- Attachment #1: Type: text/plain, Size: 2807 bytes --]
On Fri, Jul 25, 2003 at 12:18:04PM -0400, Ben Collins wrote:
> Ok, in ieee1394_core.c, when it does the "packet removed in
> abort_timedouts" could you make it print the value of jiffies, expire
> and packet->sendtime?
So, abort_timedouts() is called by the scheduler as part of work queue
handling? Every HZ or based on the expire timeout?
It looks like (packet->sendtime - jiffies) is always 99.
-Chris
ieee1394: Initiating ConfigROM request for node 00:1023
ieee1394: send packet local: ffc00140 ffc0ffff f0000400
ieee1394: TLABEL: appending packet to pending list
ieee1394: TLABEL: packet removed in abort_timedouts
ieee1394: TLABEL: jiffies 612965374, expire 98, packet->sendtime 612965275
ieee1394: received packet: ffc00140 ffc0ffff f0000400
ieee1394: send packet local: ffc00160 ffc00000 00000000 60f30404
ieee1394: TLABEL: no_waiter, returning
ieee1394: received packet: ffc00160 ffc00000 00000000 60f30404
ieee1394: TLABEL: Checking for tlabel 0
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: contents: ffc00160 ffc00000 00000000 60f30404
ieee1394: send packet local: ffc00540 ffc0ffff f0000400
ieee1394: TLABEL: appending packet to pending list
ieee1394: TLABEL: packet removed in abort_timedouts
ieee1394: TLABEL: jiffies 612965808, expire 98, packet->sendtime 612965709
ieee1394: received packet: ffc00540 ffc0ffff f0000400
ieee1394: send packet local: ffc00560 ffc00000 00000000 60f30404
ieee1394: TLABEL: no_waiter, returning
ieee1394: received packet: ffc00560 ffc00000 00000000 60f30404
ieee1394: TLABEL: Checking for tlabel 1
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: contents: ffc00560 ffc00000 00000000 60f30404
ieee1394: send packet local: ffc00940 ffc0ffff f0000400
ieee1394: TLABEL: appending packet to pending list
ieee1394: TLABEL: packet removed in abort_timedouts
ieee1394: TLABEL: jiffies 612966242, expire 98, packet->sendtime 612966143
ieee1394: received packet: ffc00940 ffc0ffff f0000400
ieee1394: send packet local: ffc00960 ffc00000 00000000 60f30404
ieee1394: TLABEL: no_waiter, returning
ieee1394: received packet: ffc00960 ffc00000 00000000 60f30404
ieee1394: TLABEL: Checking for tlabel 2
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: contents: ffc00960 ffc00000 00000000 60f30404
ieee1394: ConfigROM quadlet transaction error for node 00:1023
ieee1394: send packet 100: ffff0100 ffc0ffff f0000234 1f0000c0
ohci1394_0: Inserting packet for node 63:1023, tlabel=0, tcode=0x0, speed=0
ohci1394_0: Starting transmit DMA ctx=0
ohci1394_0: IntEvent: 00000001
ohci1394_0: Got reqTxComplete interrupt status=0x00008011
ohci1394_0: Packet sent to node 63 tcode=0x0 tLabel=0x00 ack=0x11 spd=0 data=0x1F0000C0 ctx=0
ieee1394: TLABEL: not pending or no response expected, returning
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2003-07-25 16:47 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 ` Firewire Ben Collins
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 ` Chris Ruvolo [this message]
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=20030725170255.GN23196@ruvolo.net \
--to=chris+lkml@ruvolo.net \
--cc=bcollins@debian.org \
--cc=gaxt@rogers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=sbromley@cogeco.ca \
--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).