From: Chris Moore <chris.moore@mail.com>
To: linux-kernel@vger.kernel.org
Subject: problem with sbp2 / ieee1394 in kernel 2.6.3
Date: Tue, 16 Mar 2004 00:01:53 +0100 [thread overview]
Message-ID: <16470.13793.211260.738789@chrislap.ourcpu.com> (raw)
I have a Maxtor 5000XT external ieee1394/USB2 disk drive, which I
connect to my PC's ieee1394 port. It works well with Linux under
both kernels 2.4.x and 2.6.3 for a while. I see messages like these
in syslog (under 2.6.3):
Mar 15 13:21:55 chrislap kernel: Vendor: Maxtor Model: 5000XT Rev: 0100
Mar 15 13:21:55 chrislap kernel: Type: Direct-Access ANSI SCSI revision: 06
Mar 15 13:21:55 chrislap kernel: SCSI device sda: 490232832 512-byte hdwr sectors (250999 MB)
Mar 15 13:21:55 chrislap kernel: sda: asking for cache data failed
Mar 15 13:21:55 chrislap kernel: sda: assuming drive cache: write through
Mar 15 13:21:55 chrislap kernel: /dev/scsi/host0/bus0/target0/lun0: p1 p2 p3 p4 < p5 p6 >
Mar 15 13:21:55 chrislap kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Unfortunately, at some point problems always occur. Sometimes the
drive stops working very quickly, other times I can transfer tens of
gigabytes of data to and from the drive before anything goes wrong
with it, but eventually it always breaks, under both 2.4.x and 2.6.3.
When it breaks I see messages like these in the syslog:
Mar 15 23:32:26 chrislap kernel: ieee1394: sbp2: aborting sbp2 command
Mar 15 23:32:26 chrislap kernel: Read (10) 00 04 d0 26 6f 00 00 b0 00
Mar 15 23:32:36 chrislap kernel: ieee1394: sbp2: aborting sbp2 command
Mar 15 23:32:36 chrislap kernel: Test Unit Ready 00 00 00 00 00
Mar 15 23:32:36 chrislap kernel: ieee1394: sbp2: reset requested
Mar 15 23:32:36 chrislap kernel: ieee1394: sbp2: Generating sbp2 fetch agent reset
Mar 15 23:32:46 chrislap kernel: ieee1394: sbp2: aborting sbp2 command
Mar 15 23:32:46 chrislap kernel: Test Unit Ready 00 00 00 00 00
Mar 15 23:32:46 chrislap kernel: ieee1394: sbp2: reset requested
Mar 15 23:32:46 chrislap kernel: ieee1394: sbp2: Generating sbp2 fetch agent reset
Mar 15 23:33:06 chrislap kernel: ieee1394: sbp2: aborting sbp2 command
Mar 15 23:33:06 chrislap kernel: Test Unit Ready 00 00 00 00 00
Mar 15 23:33:06 chrislap kernel: ieee1394: sbp2: reset requested
Mar 15 23:33:06 chrislap kernel: ieee1394: sbp2: Generating sbp2 fetch agent reset
Mar 15 23:33:26 chrislap kernel: ieee1394: sbp2: aborting sbp2 command
Mar 15 23:33:26 chrislap kernel: Test Unit Ready 00 00 00 00 00
Mar 15 23:33:26 chrislap kernel: scsi: Device offlined - not ready after error recovery: host 0 channel 0 id 0 lun 0
Mar 15 23:33:26 chrislap kernel: SCSI error : <0 0 0 0> return code = 0x50000
Mar 15 23:33:26 chrislap kernel: end_request: I/O error, dev sda, sector 80750191
Mar 15 23:33:26 chrislap kernel: scsi0 (0:0): rejecting I/O to offline device
Mar 15 23:33:26 chrislap kernel: Buffer I/O error on device sda2, logical block 110592
Mar 15 23:33:26 chrislap kernel: lost page write due to I/O error on sda2
Mar 15 23:33:26 chrislap kernel: scsi0 (0:0): rejecting I/O to offline device
Mar 15 23:33:26 chrislap kernel: scsi0 (0:0): rejecting I/O to offline device
Mar 15 23:33:26 chrislap kernel: Buffer I/O error on device sda2, logical block 3547
Mar 15 23:33:26 chrislap kernel: lost page write due to I/O error on sda2
Mar 15 23:33:26 chrislap kernel: Aborting journal on device sda2.
Mar 15 23:33:26 chrislap kernel: scsi0 (0:0): rejecting I/O to offline device
Mar 15 23:33:26 chrislap kernel: ext3_abort called.
Mar 15 23:33:26 chrislap kernel: EXT3-fs abort (device sda2): ext3_journal_start: Detected aborted journal
Mar 15 23:33:26 chrislap kernel: Remounting filesystem read-only
Mar 15 23:33:26 chrislap kernel: scsi0 (0:0): rejecting I/O to offline device
Mar 15 23:33:26 chrislap kernel: EXT3-fs error (device sda2): ext3_get_inode_loc: unable to read inode block - inode=327681, block=655362
When this happens I umount the firewire filesystems and then try to
"modprobe -r -v sbp2", but the modprobe command always hangs. I find
I cannot access the drive again until I reboot.
Please, if there's anything more you need to know, or anything I can
do to help diagnose this problem, just reply to this message. I would
love to see it fixed.
Chris.
next reply other threads:[~2004-03-15 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 23:01 Chris Moore [this message]
2004-03-19 7:15 ` Chris Moore
2004-03-16 3:07 Bob Gill
2004-03-18 18:03 ` Edd Dumbill
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=16470.13793.211260.738789@chrislap.ourcpu.com \
--to=chris.moore@mail.com \
--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®