Bugzilla – Bug 117692
"ieee1394: sbp2: aborting sbp2 command" on NFORCE3 chipset with external firewire hdd
Last modified: 2006-02-22 16:07:58 UTC
connecting an external ieee1394 hdd on the VIA firewire port i get following error: " Sep 18 19:14:39 pcag kernel: ieee1394: Error parsing configrom for node 1-01:1023 Sep 18 19:14:39 pcag kernel: ieee1394: The root node is not cycle master capable; selecting a new root node and resetting... Sep 18 19:14:39 pcag kernel: ieee1394: Node added: ID:BUS[1-00:1023] GUID[01ac911000003810] Sep 18 19:14:39 pcag kernel: ieee1394: Node changed: 1-00:1023 -> 1-01:1023 Sep 18 19:14:39 pcag kernel: ieee1394: unsolicited response packet received - no tlabel match Sep 18 19:14:40 pcag kernel: sbp2: $Rev: 1306 $ Ben Collins <bcollins@debian.org> Sep 18 19:14:40 pcag kernel: scsi5 : SCSI emulation for IEEE-1394 SBP-2 Devices Sep 18 19:14:41 pcag kernel: ieee1394: sbp2: Logged into SBP-2 device Sep 18 19:14:41 pcag kernel: ieee1394: Node 1-00:1023: Max speed [S400] - Max payload [2048] Sep 18 19:14:41 pcag kernel: Vendor: FUJITSU Model: MHT2040AT Rev: 0.01 Sep 18 19:14:41 pcag kernel: Type: Direct-Access ANSI SCSI revision: 02 Sep 18 19:14:41 pcag kernel: SCSI device sdd: 78140160 512-byte hdwr sectors (40008 MB) Sep 18 19:14:41 pcag kernel: sdd: got wrong page Sep 18 19:14:41 pcag kernel: sdd: assuming drive cache: write through Sep 18 19:14:41 pcag kernel: SCSI device sdd: 78140160 512-byte hdwr sectors (40008 MB) Sep 18 19:14:41 pcag kernel: sdd: got wrong page Sep 18 19:14:41 pcag kernel: sdd: assuming drive cache: write through Sep 18 19:14:41 pcag kernel: sdd: sdd1 Sep 18 19:14:41 pcag kernel: Attached scsi disk sdd at scsi5, channel 0, id 0, lun 0 Sep 18 19:14:41 pcag kernel: Attached scsi generic sg4 at scsi5, channel 0, id 0, lun 0, type 0 Sep 18 19:15:12 pcag kernel: ieee1394: sbp2: aborting sbp2 command Sep 18 19:15:12 pcag kernel: scsi5 : destination target 0, lun 0 Sep 18 19:15:12 pcag kernel: command: Read (10): 28 00 00 00 00 00 00 00 08 00 Sep 18 19:15:42 pcag kernel: ieee1394: sbp2: aborting sbp2 command Sep 18 19:15:42 pcag kernel: scsi5 : destination target 0, lun 0 Sep 18 19:15:42 pcag kernel: command: Read (10): 28 00 00 00 00 00 00 00 08 00 " hwinfo: "... 38: PCI 20c.0: 0c00 FireWire (IEEE 1394) (OHCI) [Created at pci.277] UDI: /org/freedesktop/Hal/devices/pci_1106_3044 Unique ID: 6Ogo.E799UO+3ez9 Parent ID: vuMS.fnpiWG08KJ2 SysFS ID: /devices/pci0000:00/0000:00:0e.0/0000:02:0c.0 SysFS BusID: 0000:02:0c.0 Hardware Class: firewire controller Model: "VIA IEEE 1394 Host Controller" Vendor: pci 0x1106 "VIA Technologies, Inc." Device: pci 0x3044 "IEEE 1394 Host Controller" SubVendor: pci 0x0574 SubDevice: pci 0x086c Revision: 0x46 Driver: "ohci1394" Memory Range: 0xfdefc000-0xfdefc7ff (rw,non-prefetchable) I/O Ports: 0x9000-0x907f (rw) IRQ: 5 (11684 events) Module Alias: "pci:v00001106d00003044sv00000574sd0000086Cbc0Csc00i10" Driver Info #0: Driver Status: ohci1394 is active Driver Activation Cmd: "modprobe ohci1394" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #26 (PCI bridge) " connecting the same hdd to the second ieee1394 port on a pci soundblaster card works: Sep 18 19:37:07 pcag kernel: ieee1394: Error parsing configrom for node 0-00:1023 Sep 18 19:37:07 pcag kernel: ieee1394: Node changed: 0-00:1023 -> 0-01:1023 Sep 18 19:37:08 pcag kernel: ieee1394: Node removed: ID:BUS[1-00:1023] GUID[01ac911000003810] Sep 18 19:37:08 pcag kernel: ieee1394: Node added: ID:BUS[0-00:1023] GUID[01ac911000003810] Sep 18 19:37:08 pcag kernel: scsi6 : SCSI emulation for IEEE-1394 SBP-2 Devices Sep 18 19:37:09 pcag kernel: ieee1394: sbp2: Logged into SBP-2 device Sep 18 19:37:09 pcag kernel: ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048] Sep 18 19:37:09 pcag kernel: Vendor: FUJITSU Model: MHT2040AT Rev: 0.01 Sep 18 19:37:09 pcag kernel: Type: Direct-Access ANSI SCSI revision: 02 Sep 18 19:37:09 pcag kernel: SCSI device sdd: 78140160 512-byte hdwr sectors (40008 MB) Sep 18 19:37:09 pcag kernel: sdd: got wrong page Sep 18 19:37:09 pcag kernel: sdd: assuming drive cache: write through Sep 18 19:37:09 pcag kernel: SCSI device sdd: 78140160 512-byte hdwr sectors (40008 MB) Sep 18 19:37:09 pcag kernel: sdd: got wrong page Sep 18 19:37:09 pcag kernel: sdd: assuming drive cache: write through Sep 18 19:37:09 pcag kernel: sdd: sdd1 Sep 18 19:37:09 pcag kernel: Attached scsi disk sdd at scsi6, channel 0, id 0, lun 0 Sep 18 19:37:09 pcag kernel: Attached scsi generic sg4 at scsi6, channel 0, id 0, lun 0, type 0 Sep 18 19:37:10 pcag hal-subfs-mount[7982]: SYMLINKS:: disk/by-id/ieee1394-01ac911000003810:0:0 ... hwinfo: " 36: PCI 208.2: 0c00 FireWire (IEEE 1394) (OHCI) [Created at pci.277] UDI: /org/freedesktop/Hal/devices/pci_1102_4001 Unique ID: XbSb.BcNI9WwZf01 Parent ID: vuMS.fnpiWG08KJ2 SysFS ID: /devices/pci0000:00/0000:00:0e.0/0000:02:08.2 SysFS BusID: 0000:02:08.2 Hardware Class: firewire controller Model: "Creative SB Audigy FireWire Port" Vendor: pci 0x1102 "Creative Labs" Device: pci 0x4001 "SB Audigy FireWire Port" SubVendor: pci 0x1102 "Creative Labs" SubDevice: pci 0x0010 "SB Audigy FireWire Port" Revision: 0x04 Driver: "ohci1394" Memory Range: 0xfdefe000-0xfdefe7ff (rw,non-prefetchable) Memory Range: 0xfdef4000-0xfdef7fff (rw,non-prefetchable) IRQ: 5 (11684 events) Module Alias: "pci:v00001102d00004001sv00001102sd00000010bc0Csc00i10" Driver Info #0: Driver Status: ohci1394 is active Driver Activation Cmd: "modprobe ohci1394" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #26 (PCI bridge) "
Chris, anyone in your team who could have a look?
Olaf knows the firewire bits the best I think. Olaf, does this error look familiar?
write a 1 to /sys/module/sbp2/parameters/serialize_io and see if it goes away.
Since there has been no reaction if the proposed serialize_io=1 helped and "ieee1394: sbp2: aborting sbp2 command" is even in the linux1394.org F.A.Q. ( http://www.linux1394.org/faq.php#sbp2abort ), I assume that fixed the issue. The full answer found there is this ------------------------------------------------------------------------------ Possible causes are firmware bugs of the drive, unidentified bugs in Linux, or defective hardware. Make sure the drive and bridge do not overheat, which happens easily in non-ventilated enclosures. Look for a firmware update. Alas, firmware updaters typically run on Windows or Mac OS, and some SBP-2 bridges cannot be updated at all. Try serialized sbp2 operation (see sbp2 module load parameters ). Under Linux 2.6, try the CFQ I/O scheduler: echo cfq > /sys/block/sda/queue/scheduler (Replace sda by the correct device name.) Or make CFQ the default by appending the kernel parameter "elevator=cfq" at the boot prompt or in the boot loader configuration. -------------------------------------------------------------------------------- Since the default for serialize_io has been changed to 1 in mainline since the release of 10.0, we should only see this message in 10.1 if the SBP2 bridge overheats or is defective, so I think there is not much to do for 10.1 regarding this bug. For 10.0, we could create and SDB artcile and optionally, the message could be extended from "ieee1394: sbp2: aborting sbp2 command" to "ieee1394: sbp2: aborting sbp2 command, see linux1394.org/faq.php" but since serialize_io=1 by default in 10.1, I do not account this as neccessary. Since there was no response since >3 months to the needinfo, and the fix from the FAQ is active in 10.1, and I don't see anything left do do, I'm closing this bug.
*** Bug 97594 has been marked as a duplicate of this bug. ***