firewire drive / sbp2 module

firewire drive / sbp2 module

[David Lazanja]

Hello there,

I've been trying to use a firewire external hard drive under kernel 2.6, but 
I'm not having much success.  I'm using a firewire pcmcia card by Belkin
which seems to be working properly.  The drive worked with this firewire card 
under kernel 2.4.twenty_something.

I compiled 2.6.7 using the configuration from suse's 2.6.5-7.95-default kernel 
but still have no success.  All of the correct modules are loading.

>From the kernel messages (below), it seems that sbp2 is failing.  I was 
looking around on the list and found some others are also having problems
with sbp2.  I'm trying to find out if this is a known general problem under 
2.6 or if it's specific to the drive that I'm using (Buslink 80GB usb2 / 
firewire combo).

I'm using SuSE 9.1 and found on the mailing list there that some claim to have 
success with firewire drives.  I don't know??

One other thing.  I noticed that it takes maybe 20 or 40 seconds sbp2 module
to load.  Once it loads the errors are reported but I can see the attached 
scsi device under /proc/scsi/scsi:

---
Attached devices:
Host: scsi4 Channel: 00 Id: 00 Lun: 00
  Vendor: SAMSUNG  Model: SP0802N          Rev:
  Type:   Direct-Access                    ANSI SCSI revision: 06
---

Below are the kernel messages.

Any information will be greatly appreciated.
Thanks in advance.

--------------------------------
Kernel Messages from syslog:
--------------------------------

Jul 18 23:08:50 linux kernel: sbp2: $Rev: 1219 $ Ben Collins 
<bcollins@debian.org>
Jul 18 23:08:50 linux kernel: scsi0 : SCSI emulation for IEEE-1394 SBP-2 
Devices
Jul 18 23:08:51 linux kernel: ieee1394: sbp2: Logged into SBP-2 device
Jul 18 23:08:51 linux kernel: ieee1394: Node 0-00:1023: Max speed [S400] - Max 
payload [2048]
Jul 18 23:08:51 linux kernel:   Vendor: SAMSUNG   Model: SP0802N           
Rev:
Jul 18 23:08:51 linux kernel:   Type:   Direct-Access                      
ANSI SCSI revision: 06
Jul 18 23:08:51 linux kernel: SCSI device sda: 156368016 512-byte hdwr sectors 
(80060 MB)
Jul 18 23:08:51 linux kernel: sda: asking for cache data failed
Jul 18 23:08:51 linux kernel: sda: assuming drive cache: write through
Jul 18 23:09:21 linux kernel:  sda:<3>ieee1394: sbp2: aborting sbp2 command
Jul 18 23:09:21 linux kernel: Read (10) 00 00 00 00 00 00 00 08 00
Jul 18 23:09:31 linux kernel: ieee1394: sbp2: aborting sbp2 command
Jul 18 23:09:31 linux kernel: Test Unit Ready 00 00 00 00 00
Jul 18 23:09:31 linux kernel: ieee1394: sbp2: reset requested
Jul 18 23:09:31 linux kernel: ieee1394: sbp2: Generating sbp2 fetch agent 
reset
Jul 18 23:09:41 linux kernel: ieee1394: sbp2: aborting sbp2 command
Jul 18 23:09:41 linux kernel: Test Unit Ready 00 00 00 00 00
Jul 18 23:09:41 linux kernel: ieee1394: sbp2: reset requested
Jul 18 23:09:41 linux kernel: ieee1394: sbp2: Generating sbp2 fetch agent 
reset
Jul 18 23:10:01 linux kernel: ieee1394: sbp2: aborting sbp2 command
Jul 18 23:10:01 linux kernel: Test Unit Ready 00 00 00 00 00
Jul 18 23:10:01 linux kernel: ieee1394: sbp2: reset requested
Jul 18 23:10:01 linux kernel: ieee1394: sbp2: Generating sbp2 fetch agent 
reset
Jul 18 23:10:21 linux kernel: ieee1394: sbp2: aborting sbp2 command
Jul 18 23:10:21 linux kernel: Test Unit Ready 00 00 00 00 00
Jul 18 23:10:21 linux kernel: scsi: Device offlined - not ready after error 
recovery: host 0 channel 0 id 0 lun 0
Jul 18 23:10:21 linux kernel: SCSI error : <0 0 0 0> return code = 0x50000
Jul 18 23:10:21 linux kernel: end_request: I/O error, dev sda, sector 0
Jul 18 23:10:21 linux kernel: Buffer I/O error on device sda, logical block 0
Jul 18 23:10:21 linux kernel: scsi0 (0:0): rejecting I/O to offline device
Jul 18 23:10:21 linux kernel: Buffer I/O error on device sda, logical block 0
Jul 18 23:10:21 linux kernel: scsi0 (0:0): rejecting I/O to offline device
Jul 18 23:10:21 linux kernel: Buffer I/O error on device sda, logical block 
19546001
Jul 18 23:10:21 linux kernel: scsi0 (0:0): rejecting I/O to offline device
Jul 18 23:10:21 linux kernel: Buffer I/O error on device sda, logical block 
19546001
Jul 18 23:10:21 linux kernel: scsi0 (0:0): rejecting I/O to offline device
Jul 18 23:10:21 linux kernel: Buffer I/O error on device sda, logical block 0
Jul 18 23:10:21 linux kernel: ldm_validate_partition_table(): Disk read 
failed.
Jul 18 23:10:21 linux kernel:  unsupported disk (sda)
Jul 18 23:10:21 linux kernel: scsi0 (0:0): rejecting I/O to offline device
Jul 18 23:10:21 linux kernel: Buffer I/O error on device sda, logical block 0
Jul 18 23:10:21 linux kernel:  unable to read partition table
Jul 18 23:10:21 linux kernel: Attached scsi disk sda at scsi0, channel 0, id 
0, lun 0
Jul 18 23:10:21 linux kernel: Attached scsi generic sg0 at scsi0, channel 0, 
id 0, lun 0,  type 0

-- 
# Department of Applied Physics and Applied Mathematics
# Columbia University

Re: firewire drive / sbp2 module

[Craig I. Hagan]

> I compiled 2.6.7 using the configuration from suse's 2.6.5-7.95-default kernel 
> but still have no success.  All of the correct modules are loading.

I'm using stock 2.6.7 on top of gentoo and have had no problems with firewire
drives (i'm using a pci fw card)

> >From the kernel messages (below), it seems that sbp2 is failing.  I was 
> looking around on the list and found some others are also having problems
> with sbp2.  I'm trying to find out if this is a known general problem under 
> 2.6 or if it's specific to the drive that I'm using (Buslink 80GB usb2 / 
> firewire combo).

I've not had problems with 2.6.x and firewire, otoh, i'm running pci vs. pcmcia
devices. have you confirmed your drive works on a different system or os?

-- craig

Re: firewire drive / sbp2 module

[David Lazanja]

Craig I. Hagan wrote:
>>I compiled 2.6.7 using the configuration from suse's 2.6.5-7.95-default kernel 
>>but still have no success.  All of the correct modules are loading.
> 
> 
> I'm using stock 2.6.7 on top of gentoo and have had no problems with firewire
> drives (i'm using a pci fw card)
> 
> 

Just wanted to clarify, I compiled a "vanilla" kernel from www.kernel.org.
I used the config file from suse so that I do not have to go through all
the configuration options.

>>>From the kernel messages (below), it seems that sbp2 is failing.  I was 
>>looking around on the list and found some others are also having problems
>>with sbp2.  I'm trying to find out if this is a known general problem under 
>>2.6 or if it's specific to the drive that I'm using (Buslink 80GB usb2 / 
>>firewire combo).
> 
> 
> I've not had problems with 2.6.x and firewire, otoh, i'm running pci vs. pcmcia
> devices. have you confirmed your drive works on a different system or os?
> 
The drive works with usb1 using kernel 2.4.xx on the same laptop.
It works with usb2 (pci) using kernel 2.4.xx on a different laptop.
The drive worked with the Belkin F5U512 pcmcia firewire using kernel 
2.4.xx on both laptops.

I'm trying to determine if the firewire modules are causing the problem 
or if it's sbp2.  Below is part of the kernel log.  The only thing that 
I can find about the firewrie card is
"ieee1394: unsolicited response packet received - no tlabel match".  I 
don't know if this os OK.

Kernel Log:

Jul 18 18:32:21 linux kernel: ieee1394: Initialized config rom entry 
`ip1394'
Jul 18 18:32:21 linux kernel: ohci1394: $Rev: 1203 $ Ben Collins 
<bcollins@debian.org>
Jul 18 18:32:21 linux kernel: PCI: Enabling device 0000:02:00.0 (0000 -> 
0002)
Jul 18 18:32:21 linux kernel: PCI: Setting latency timer of device 
0000:02:00.0 to 64
Jul 18 18:32:21 linux kernel: ohci1394: fw-host0: OHCI-1394 1.1 (PCI): 
IRQ=[9]  MMIO=[18804000-188047ff]  Max Packet=[2048]
Jul 18 18:32:22 linux kernel: ieee1394: Host added: ID:BUS[0-00:1023] 
GUID[000030bd00000000]
Jul 18 18:33:07 linux kernel: ieee1394: Node added: ID:BUS[0-00:1023] 
GUID[0006ca0e04002625]
Jul 18 18:33:07 linux kernel: ieee1394: Node changed: 0-00:1023 -> 0-01:1023
Jul 18 18:33:07 linux kernel: ieee1394: unsolicited response packet 
received - no tlabel match
Jul 18 18:33:12 linux kernel: sbp2: $Rev: 1205 $ Ben Collins 
<bcollins@debian.org>
Jul 18 18:33:12 linux kernel: scsi4 : SCSI emulation for IEEE-1394 SBP-2 
Devices
Jul 18 18:33:13 linux kernel: ieee1394: sbp2: Logged into SBP-2 device
Jul 18 18:33:13 linux kernel: ieee1394: Node 0-00:1023: Max speed [S400] 
- Max payload [2048]
Jul 18 18:33:13 linux kernel:   Vendor: SAMSUNG   Model: SP0802N 
    Rev:
Jul 18 18:33:13 linux kernel:   Type:   Direct-Access 
    ANSI SCSI revision: 06
Jul 18 18:33:13 linux kernel: SCSI device sda: 156368016 512-byte hdwr 
sectors (80060 MB)
Jul 18 18:33:13 linux kernel: sda: asking for cache data failed
Jul 18 18:33:13 linux kernel: sda: assuming drive cache: write through
Jul 18 18:33:43 linux kernel:  sda:<3>ieee1394: sbp2: aborting sbp2 command
Jul 18 18:33:43 linux kernel: Read (10) 00 00 00 00 00 00 00 08 00
Jul 18 18:34:13 linux kernel: ieee1394: sbp2: aborting sbp2 command
Jul 18 18:34:13 linux kernel: Test Unit Ready 00 00 00 00 00
Jul 18 18:34:13 linux kernel: ieee1394: sbp2: reset requested
Jul 18 18:34:13 linux kernel: ieee1394: sbp2: Generating sbp2 fetch 
agent reset
Jul 18 18:34:43 linux kernel: ieee1394: sbp2: aborting sbp2 command