The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Felix von Leitner <felix-kernel@fefe.de>
To: linux-kernel@vger.kernel.org
Subject: ieee1394: unsolicited response packet received - no tlabel match
Date: Tue, 22 Jun 2004 23:38:30 +0200	[thread overview]
Message-ID: <20040622213830.GA11770@codeblau.de> (raw)

This is an excerpt from my dmesg.  I am using a large Maxtor firewire
hard disk as VCR storage.  This happens only when I read large files
from the external firewire disk, not when watching an AVI movie on it
(i.e. reading it slowly).

Jun 22 22:58:43 hellhound ieee1394: sbp2: aborting sbp2 command
Jun 22 22:58:43 hellhound 0x28 00 02 3c 93 a5 00 00 01 00 
Jun 22 22:58:43 hellhound ieee1394: sbp2: aborting sbp2 command
Jun 22 22:58:43 hellhound 0x28 00 02 3c 93 a6 00 00 01 00 
Jun 22 22:58:43 hellhound ieee1394: sbp2: aborting sbp2 command
Jun 22 22:58:43 hellhound 0x28 00 02 3c 93 a7 00 00 01 00 
Jun 22 22:58:43 hellhound ieee1394: sbp2: aborting sbp2 command
Jun 22 22:58:43 hellhound 0x28 00 02 3c 93 a8 00 00 01 00 
Jun 22 22:58:43 hellhound ieee1394: sbp2: aborting sbp2 command
Jun 22 22:58:43 hellhound 0x28 00 02 3c 93 a9 00 00 01 00 
Jun 22 22:58:43 hellhound ieee1394: sbp2: aborting sbp2 command
Jun 22 22:58:43 hellhound 0x28 00 02 3c 93 aa 00 00 01 00 
Jun 22 22:58:43 hellhound ieee1394: sbp2: aborting sbp2 command
Jun 22 22:58:43 hellhound 0x28 00 02 3c 93 ab 00 00 01 00 
Jun 22 22:58:43 hellhound ieee1394: sbp2: aborting sbp2 command
Jun 22 22:58:43 hellhound 0x28 00 02 3c 93 ac 00 00 01 00 
Jun 22 23:25:40 hellhound ieee1394: unsolicited response packet received - no tlabel match
Jun 22 23:26:44 hellhound ieee1394: sbp2: aborting sbp2 command
Jun 22 23:26:44 hellhound 0x28 00 13 82 4b 76 00 00 80 00 
Jun 22 23:26:44 hellhound ieee1394: sbp2: aborting sbp2 command
Jun 22 23:26:44 hellhound 0x28 00 13 82 4b f6 00 00 01 00 
Jun 22 23:26:44 hellhound ieee1394: sbp2: aborting sbp2 command
Jun 22 23:26:44 hellhound 0x28 00 13 82 4b f7 00 00 01 00 
Jun 22 23:26:44 hellhound ieee1394: sbp2: aborting sbp2 command
Jun 22 23:26:44 hellhound 0x28 00 13 82 4b f8 00 00 01 00 
Jun 22 23:26:44 hellhound ieee1394: sbp2: aborting sbp2 command
Jun 22 23:26:44 hellhound 0x28 00 13 82 4b f9 00 00 01 00 
Jun 22 23:26:44 hellhound ieee1394: sbp2: aborting sbp2 command
Jun 22 23:26:44 hellhound 0x28 00 13 82 4b fa 00 00 01 00 
Jun 22 23:26:44 hellhound ieee1394: sbp2: aborting sbp2 command
Jun 22 23:26:44 hellhound 0x28 00 13 82 4b fb 00 00 01 00 
Jun 22 23:26:44 hellhound ieee1394: sbp2: aborting sbp2 command
Jun 22 23:26:44 hellhound 0x28 00 13 82 4b fc 00 00 01 00 
Jun 22 23:29:34 hellhound ieee1394: unsolicited response packet received - no tlabel match
Jun 22 23:33:06 hellhound ieee1394: sbp2: aborting sbp2 command
Jun 22 23:33:06 hellhound 0x28 00 1c b3 fe ed 00 00 80 00 
Jun 22 23:33:06 hellhound ieee1394: sbp2: aborting sbp2 command
Jun 22 23:33:06 hellhound 0x28 00 1c b3 ff 6d 00 00 01 00 
Jun 22 23:33:06 hellhound ieee1394: sbp2: aborting sbp2 command
Jun 22 23:33:06 hellhound 0x28 00 1c b3 ff 6e 00 00 01 00 
Jun 22 23:33:06 hellhound ieee1394: sbp2: aborting sbp2 command
Jun 22 23:33:06 hellhound 0x28 00 1c b3 ff 6f 00 00 01 00 
Jun 22 23:33:06 hellhound ieee1394: sbp2: aborting sbp2 command
Jun 22 23:33:06 hellhound 0x28 00 1c b3 ff 70 00 00 01 00 
Jun 22 23:33:06 hellhound ieee1394: sbp2: aborting sbp2 command
Jun 22 23:33:06 hellhound 0x28 00 1c b3 ff 71 00 00 01 00 

[and so on]

After 20-30 seconds, everything gets back to normal.  The copied files
appear intact despite these timeouts.  Known problem?  Is my hardware
getting bad?

Felix

             reply	other threads:[~2004-06-22 21:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-22 21:38 Felix von Leitner [this message]
2004-06-23  0:37 ` ieee1394: unsolicited response packet received - no tlabel match 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=20040622213830.GA11770@codeblau.de \
    --to=felix-kernel@fefe.de \
    --cc=linux-kernel@vger.kernel.org \
    /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