From: Chris Moore <chris.moore@mail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: problem with sbp2 / ieee1394 in kernel 2.6.3
Date: Fri, 19 Mar 2004 08:15:11 +0100 [thread overview]
Message-ID: <16474.40447.453039.89445@chrislap.ourcpu.com> (raw)
In-Reply-To: <16470.13793.211260.738789@chrislap.ourcpu.com>
Bob Gill, Mon Mar 15 2004 - 22:10:19 EST:
> There were a lot of changes to ieee1394 between 2.6.3 and 2.6.4, and
> haven't seen sbp2 fail since (two or three patches) before
> 2.6.4. Try the 2.6.4 kernel (or newer) and see if that helps.
I just compiled 2.6.4. It fails just the same as in 2.4.x and 2.6.3,
but this time I got a message I hadn't noticed before - the first
line, the "unsolicited response" message is new to me:
Mar 19 07:48:10 chrislap kernel: ieee1394: unsolicited response packet received - no tlabel match
Mar 19 07:48:51 chrislap kernel: ieee1394: sbp2: aborting sbp2 command
Mar 19 07:48:51 chrislap kernel: Read (10) 00 06 b5 82 bf 00 00 f8 00
Mar 19 07:49:01 chrislap kernel: ieee1394: sbp2: aborting sbp2 command
Mar 19 07:49:01 chrislap kernel: Test Unit Ready 00 00 00 00 00
Mar 19 07:49:01 chrislap kernel: ieee1394: sbp2: aborting sbp2 command
Mar 19 07:49:01 chrislap kernel: Read (10) 00 06 b5 83 b7 00 00 08 00
Mar 19 07:49:11 chrislap kernel: ieee1394: sbp2: aborting sbp2 command
Mar 19 07:49:11 chrislap kernel: Test Unit Ready 00 00 00 00 00
Mar 19 07:49:11 chrislap kernel: ieee1394: sbp2: reset requested
Mar 19 07:49:11 chrislap kernel: ieee1394: sbp2: Generating sbp2 fetch agent reset
Mar 19 07:49:21 chrislap kernel: ieee1394: sbp2: aborting sbp2 command
Mar 19 07:49:21 chrislap kernel: Test Unit Ready 00 00 00 00 00
Mar 19 07:49:21 chrislap kernel: ieee1394: sbp2: reset requested
Mar 19 07:49:21 chrislap kernel: ieee1394: sbp2: Generating sbp2 fetch agent reset
Mar 19 07:49:41 chrislap kernel: ieee1394: sbp2: aborting sbp2 command
Mar 19 07:49:41 chrislap kernel: Test Unit Ready 00 00 00 00 00
Mar 19 07:49:51 chrislap kernel: ieee1394: sbp2: aborting sbp2 command
Mar 19 07:49:51 chrislap kernel: Test Unit Ready 00 00 00 00 00
Mar 19 07:49:51 chrislap kernel: ieee1394: sbp2: reset requested
[...]
I umounted the drive - got some errors, but it umounted:
[root@chrislap firewire]# umount g
messages:Mar 19 07:55:12 chrislap kernel: scsi1 (1:0): rejecting I/O to offline device
messages:Mar 19 07:55:12 chrislap kernel: Buffer I/O error on device sda2, logical block 524
messages:Mar 19 07:55:12 chrislap kernel: lost page write due to I/O error on sda2
[root@chrislap firewire]#
but then modprobe hung:
[root@chrislap firewire]# modprobe -r -v sbp2
unloading the sbp2 module:
rmmod /lib/modules/2.6.4/kernel/drivers/ieee1394/sbp2.ko
^--note no root prompt came back
So what should I do next? Incidentally, I don't suppose it is of any
interest, but the drive has a USB 2 interface too. My PC doesn't
have a USB 2 port, but it does have USB 1. I've managed to read the
whole disk using the USB 1 interface (albeit VERY slowly). Perhaps
that's interesting...
Chris.
next prev parent reply other threads:[~2004-03-19 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 23:01 problem with sbp2 / ieee1394 in kernel 2.6.3 Chris Moore
2004-03-19 7:15 ` Chris Moore [this message]
-- strict thread matches above, loose matches on Subject: below --
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=16474.40447.453039.89445@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