From: Sebastian Zimmermann <sebastian@expires1203.datenknoten.de>
To: linux-kernel@vger.kernel.org
Subject: ieee1394: sbp2: sbp2util_allocate_request_packet
Date: 05 Mar 2003 22:08:08 +0100 [thread overview]
Message-ID: <1046898487.3493.24.camel@coruscant.datenknoten.de> (raw)
Hello,
I have a problem using an external firewire harddrive. When writing to
the disk (badblocks -w) I get an error message about every minute:
kernel: ieee1394: sbp2: sbp2util_allocate_request_packet - no packets
available!
kernel: ieee1394: sbp2: sbp2util_allocate_write_request_packet failed
kernel: ieee1394: sbp2: aborting sbp2 command
kernel: Write (10) 00 09 51 b4 4a 00 00 fe 00
This by itself is - except for small pauses once and then - no problem.
But when writing much data (dd for 40 GB), it gets worse after some
time:
(log continued)
kernel: ieee1394: sbp2: aborting sbp2 command
kernel: Read (10) 00 08 b3 f2 5a 00 00 fe 00
kernel: ieee1394: sbp2: aborting sbp2 command
kernel: Test Unit Ready 00 00 00 00 00
kernel: ieee1394: sbp2: reset requested
kernel: ieee1394: sbp2: Generating sbp2 fetch agent reset
kernel: ieee1394: sbp2: aborting sbp2 command
kernel: Test Unit Ready 00 00 00 00 00
kernel: ieee1394: sbp2: reset requested
kernel: ieee1394: sbp2: Generating sbp2 fetch agent reset
kernel: ieee1394: sbp2: aborting sbp2 command
kernel: Test Unit Ready 00 00 00 00 00
kernel: scsi: device set offline - not ready or command retry failed
after bus reset: host 0 channel 0 id 0 lun 0
SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 50000
kernel: I/O error: dev 08:02, sector 67838424
kernel: I/O error: dev 08:02, sector 67838426
[...]
I am using kernel.org's 2.4.20 kernel.
Thanks for your help!
Sebastian
next reply other threads:[~2003-03-05 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 21:08 Sebastian Zimmermann [this message]
2003-03-05 21:21 ` Ben Collins
2003-03-05 21:39 ` William Stearns
2003-03-05 22:16 ` 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=1046898487.3493.24.camel@coruscant.datenknoten.de \
--to=sebastian@expires1203.datenknoten.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
all inboxes | Powered by JetHome®