Thread: Firewire errors with Freecom Hard Drive Quattro and linux kernel 3.13 rc8: firewire_sbp2 fw1.0: sta
Brought to you by:
aeb,
bencollins
From: <pho...@ya...> - 2014-01-15 21:11:22
|
Hello, I still do have the problems with my new Freecom Hard Drive on its firewire port. Anyway, I thought I might try a new kernel to see if the problems would go away. However the errors are still coming. This is what I get from dmesg: [ 9479.962832] firewire_sbp2 fw1.0: status write for unknown ORB [ 9507.242920] firewire_sbp2 fw1.0: status write for unknown ORB [ 9516.771148] firewire_sbp2 fw1.0: status write for unknown ORB [ 9526.468622] firewire_sbp2 fw1.0: status write for unknown ORB [ 9536.401621] firewire_sbp2 fw1.0: status write for unknown ORB [ 9548.284219] firewire_sbp2 fw1.0: status write for unknown ORB [ 9558.161014] firewire_sbp2 fw1.0: status write for unknown ORB [ 9569.873588] firewire_sbp2 fw1.0: status write for unknown ORB [ 9580.387676] firewire_sbp2 fw1.0: status write for unknown ORB [ 9601.481144] firewire_sbp2 fw1.0: status write for unknown ORB [ 9611.816042] firewire_sbp2 fw1.0: status write for unknown ORB [ 9621.470940] firewire_sbp2 fw1.0: status write for unknown ORB [ 9631.515208] firewire_sbp2 fw1.0: status write for unknown ORB [ 9642.887931] firewire_sbp2 fw1.0: status write for unknown ORB [ 9714.282519] firewire_sbp2 fw1.0: status write for unknown ORB [ 9739.550211] firewire_sbp2 fw1.0: status write for unknown ORB [ 9766.211506] firewire_sbp2 fw1.0: status write for unknown ORB [ 9786.250357] firewire_sbp2 fw1.0: status write for unknown ORB [ 9795.777075] firewire_sbp2 fw1.0: status write for unknown ORB [ 9805.536467] firewire_sbp2 fw1.0: status write for unknown ORB [ 9824.852129] firewire_sbp2 fw1.0: status write for unknown ORB [ 9834.522667] firewire_sbp2 fw1.0: status write for unknown ORB $> uname -a Linux tuxtux 3.13.0-031300rc8-generic #201401120535 SMP Sun Jan 12 10:36:21 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Any ideas, hints what I could try to make this work ? BR P. |
From: <pho...@ya...> - 2014-01-15 21:42:39
|
[ 9479.962832] firewire_sbp2 fw1.0: status write for unknown ORB [ 9507.242920] firewire_sbp2 fw1.0: status write for unknown ORB [ 9516.771148] firewire_sbp2 fw1.0: status write for unknown ORB [ 9526.468622] firewire_sbp2 fw1.0: status write for unknown ORB [ 9536.401621] firewire_sbp2 fw1.0: status write for unknown ORB [ 9548.284219] firewire_sbp2 fw1.0: status write for unknown ORB [ 9558.161014] firewire_sbp2 fw1.0: status write for unknown ORB [ 9569.873588] firewire_sbp2 fw1.0: status write for unknown ORB [ 9580.387676] firewire_sbp2 fw1.0: status write for unknown ORB [ 9601.481144] firewire_sbp2 fw1.0: status write for unknown ORB [ 9611.816042] firewire_sbp2 fw1.0: status write for unknown ORB [ 9621.470940] firewire_sbp2 fw1.0: status write for unknown ORB [ 9631.515208] firewire_sbp2 fw1.0: status write for unknown ORB [ 9642.887931] firewire_sbp2 fw1.0: status write for unknown ORB [ 9714.282519] firewire_sbp2 fw1.0: status write for unknown ORB [ 9739.550211] firewire_sbp2 fw1.0: status write for unknown ORB [ 9766.211506] firewire_sbp2 fw1.0: status write for unknown ORB [ 9786.250357] firewire_sbp2 fw1.0: status write for unknown ORB [ 9795.777075] firewire_sbp2 fw1.0: status write for unknown ORB [ 9805.536467] firewire_sbp2 fw1.0: status write for unknown ORB [ 9824.852129] firewire_sbp2 fw1.0: status write for unknown ORB [ 9834.522667] firewire_sbp2 fw1.0: status write for unknown ORB [ 9844.223044] firewire_sbp2 fw1.0: status write for unknown ORB [ 9854.082187] firewire_sbp2 fw1.0: status write for unknown ORB [ 9864.267172] firewire_sbp2 fw1.0: status write for unknown ORB [ 9873.993240] firewire_sbp2 fw1.0: status write for unknown ORB [ 9883.731921] firewire_sbp2 fw1.0: status write for unknown ORB [ 9898.453387] firewire_sbp2 fw1.0: status write for unknown ORB [ 9933.909223] firewire_sbp2 fw1.0: status write for unknown ORB [ 9973.925368] firewire_sbp2 fw1.0: status write for unknown ORB [ 9983.467125] firewire_sbp2 fw1.0: status write for unknown ORB [10003.996977] firewire_sbp2 fw1.0: status write for unknown ORB [10019.291551] firewire_sbp2 fw1.0: status write for unknown ORB [10029.879373] firewire_core 0000:03:01.4: phy config: new root=ffc0, gap_count=63 [10030.776064] firewire_ohci 0000:03:01.4: failed to read phy reg 5 [10030.776075] CPU: 0 PID: 9634 Comm: kworker/0:0 Tainted: GF O 3.13.0-031300rc8-generic #201401120535 [10030.776079] Hardware name: Dell Inc. Latitude D630 / , BIOS A19 06/04/2013 [10030.776109] Workqueue: events bm_work [firewire_core] [10030.776114] 0000000000000067 ffff8801ea6e5cb8 ffffffff81733572 0000000000000000 [10030.776121] ffff880210506000 ffff8801ea6e5ce8 ffffffffa004dbec ffff8801ea6e5d28 [10030.776128] 0000000000000005 ffff880210506000 0000000000000000 ffff8801ea6e5d18 [10030.776134] Call Trace: [10030.776146] [<ffffffff81733572>] dump_stack+0x46/0x58 [10030.776159] [<ffffffffa004dbec>] read_phy_reg+0x8c/0xd0 [firewire_ohci] [10030.776170] [<ffffffffa004dc5d>] update_phy_reg+0x2d/0x70 [firewire_ohci] [10030.776180] [<ffffffffa004dced>] ohci_update_phy_reg+0x4d/0x80 [firewire_ohci] [10030.776192] [<ffffffffa003312c>] bm_work+0x50c/0x650 [firewire_core] [10030.776200] [<ffffffff8108442f>] process_one_work+0x17f/0x4c0 [10030.776210] [<ffffffff8108565b>] worker_thread+0x11b/0x3d0 [10030.776213] [<ffffffff81085540>] ? manage_workers.isra.21+0x190/0x190 [10030.776216] [<ffffffff8108c5b9>] kthread+0xc9/0xe0 [10030.776219] [<ffffffff8108c4f0>] ? flush_kthread_worker+0xb0/0xb0 [10030.776222] [<ffffffff817489bc>] ret_from_fork+0x7c/0xb0 [10030.776224] [<ffffffff8108c4f0>] ? flush_kthread_worker+0xb0/0xb0 [10031.876070] firewire_sbp2 fw2.0: ORB reply timed out, rcode 0x00 [10031.876081] firewire_sbp2 fw2.0: failed to reconnect [10031.876103] firewire_sbp2 fw1.0: ORB reply timed out, rcode 0x00 [10031.876109] firewire_sbp2 fw1.0: failed to reconnect [10034.076070] firewire_sbp2 fw2.0: ORB reply timed out, rcode 0x00 [10034.076094] firewire_sbp2 fw1.0: ORB reply timed out, rcode 0x00 [10039.097216] firewire_core 0000:03:01.4: unsolicited response (source ffc1, tlabel 24) [10039.098072] firewire_core 0000:03:01.4: unsolicited response (source ffc1, tlabel 26) [10039.116062] firewire_sbp2 fw1.0: status write for unknown ORB [10039.118160] firewire_sbp2 fw2.0: status write for unknown ORB [10039.120480] firewire_sbp2 fw2.0: status write for unknown ORB [10040.102529] firewire_sbp2 fw1.0: status write for unknown ORB [10040.121964] firewire_sbp2 fw1.0: logged in to LUN 0000 (0 retries) [10064.076076] firewire_sbp2 fw2.0: ORB reply timed out, rcode 0x11 [10064.276659] firewire_core 0000:03:01.4: unsolicited response (source ffc1, tlabel 27) [10064.278349] firewire_sbp2 fw2.0: error status: 0:10 [10064.279086] firewire_core 0000:03:01.4: unsolicited response (source ffc1, tlabel 28) [10064.310995] firewire_sbp2 fw2.0: logged in to LUN 0000 (1 retries) [10064.311684] firewire_core 0000:03:01.4: unsolicited response (source ffc1, tlabel 29) > > Hello, > > I still do have the problems with my new Freecom Hard Drive on its > firewire port. Anyway, I thought I might try a new kernel to see if the > problems would go away. However the errors are still coming. > > This is what I get from dmesg: > > [ 9479.962832] firewire_sbp2 fw1.0: status write for unknown ORB > [ 9507.242920] firewire_sbp2 fw1.0: status write for unknown ORB > [ 9516.771148] firewire_sbp2 fw1.0: status write for unknown ORB > [ 9526.468622] firewire_sbp2 fw1.0: status write for unknown ORB > [ 9536.401621] firewire_sbp2 fw1.0: status write for unknown ORB > [ 9548.284219] firewire_sbp2 fw1.0: status write for unknown ORB > [ 9558.161014] firewire_sbp2 fw1.0: status write for unknown ORB > [ 9569.873588] firewire_sbp2 fw1.0: status write for unknown ORB > [ 9580.387676] firewire_sbp2 fw1.0: status write for unknown ORB > [ 9601.481144] firewire_sbp2 fw1.0: status write for unknown ORB > [ 9611.816042] firewire_sbp2 fw1.0: status write for unknown ORB > [ 9621.470940] firewire_sbp2 fw1.0: status write for unknown ORB > [ 9631.515208] firewire_sbp2 fw1.0: status write for unknown ORB > [ 9642.887931] firewire_sbp2 fw1.0: status write for unknown ORB > [ 9714.282519] firewire_sbp2 fw1.0: status write for unknown ORB > [ 9739.550211] firewire_sbp2 fw1.0: status write for unknown ORB > [ 9766.211506] firewire_sbp2 fw1.0: status write for unknown ORB > [ 9786.250357] firewire_sbp2 fw1.0: status write for unknown ORB > [ 9795.777075] firewire_sbp2 fw1.0: status write for unknown ORB > [ 9805.536467] firewire_sbp2 fw1.0: status write for unknown ORB > [ 9824.852129] firewire_sbp2 fw1.0: status write for unknown ORB > [ 9834.522667] firewire_sbp2 fw1.0: status write for unknown ORB > > $> uname -a > Linux tuxtux 3.13.0-031300rc8-generic #201401120535 SMP Sun Jan 12 > 10:36:21 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux > > Any ideas, hints what I could try to make this work ? > > BR > P. > > > ------------------------------------------------------------------------------ > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > Learn Why More Businesses Are Choosing CenturyLink Cloud For > Critical Workloads, Development Environments & Everything In Between. > Get a Quote or Start a Free Trial Today. > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > _______________________________________________ > mailing list Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux1394-user > |
From: Stefan R. <st...@s5...> - 2014-01-18 20:53:45
|
On Jan 15 pho...@ya... wrote: > > I still do have the problems with my new Freecom Hard Drive on its > > firewire port. Anyway, I thought I might try a new kernel to see if the > > problems would go away. However the errors are still coming. [...] Thanks for testing the most recent kernel. Overall it looks like a hardware problem to me, for example due to a poorly designed circuit board in the Freecom Quattro. Some customer reviews of the Freecom Quattro 3.0 at amazon.co.uk report unreliable operation via FireWire (in contrast to USB or eSATA), especially when daisy-chained with more FireWire devices, but also when attached alone. Some questions: You wrote earlier that you used older disks successfully. Did you use them at the very same laptop? Please send the file /sys/bus/firewire/devices/fw?/config_rom which corresponds with the Freecom Quattro. This is a binary file; if you want you can transform it into a human-readable text before posting by means of the script "crpp" from http://me.in-berlin.de/~s5r6/linux1394/utils/. Also, please generate a more verbose kernel log from a session with these I/O errors, by running sudo dd of=/sys/module/firewire_ohci/parameters/debug <<< 2 before you attach the Freecom Quattro, then reproduce the I/O errors. Lastly, if you have the means to compile C programs on this laptop, it would interesting to see the output of the program lsfirewirephy from https://code.google.com/p/jujuutils/. -- Stefan Richter -=====-====- ---= =--=- http://arcgraph.de/sr/ |
From: <pho...@ya...> - 2014-01-19 11:44:47
|
Hello Stefan, thanks for getting back to me. I am currently away from work and the new 4gb Freecom disk, but will be back with the disk on Wednesday. I can and will do all the things you suggested. I can compile c without problems. I this laptop with the firewire port I am using two older Freecom Quattro disks (ones with USB 2.0 connector in contrast to the new one with USB 3.0), they do work fine without problems, it does not matter whether I connect them directly or if I daisy chain them. I have also used a Western Digital MyBook Studio disk (silver enclosure) with this particular laptop earlier without any problems. Could you recommend some very good firewire cables, a certain manufacturer maybe so that I could eliminate that potential problem? I currently got the cables supplied with the freecom and western digital drives, plus some from reichelt.de and some new delock ones bought from amazon. They all work fine with the older freecom drives, but not with the new 4tb freecom drive. I saw that I have a firewire port on another computer with an asus motherboard. I will try the freecom disk there next week too. On this google code webpage https://code.google.com/p/jujuutils/ is this requirement "package requires the new "Juju" FireWire stack.". Does the new kernel use that juju firewire stack ? Thanks Best regards > On Jan 15 pho...@ya... wrote: >>> I still do have the problems with my new Freecom Hard Drive on its >>> firewire port. Anyway, I thought I might try a new kernel to see if the >>> problems would go away. However the errors are still coming. > [...] > > Thanks for testing the most recent kernel. > > Overall it looks like a hardware problem to me, for example due to a poorly > designed circuit board in the Freecom Quattro. Some customer reviews of > the Freecom Quattro 3.0 at amazon.co.uk report unreliable operation via > FireWire (in contrast to USB or eSATA), especially when daisy-chained with > more FireWire devices, but also when attached alone. > > Some questions: > > You wrote earlier that you used older disks successfully. Did you use > them at the very same laptop? > > Please send the file /sys/bus/firewire/devices/fw?/config_rom which > corresponds with the Freecom Quattro. This is a binary file; if you want > you can transform it into a human-readable text before posting by means of > the script "crpp" from http://me.in-berlin.de/~s5r6/linux1394/utils/. > > Also, please generate a more verbose kernel log from a session with these > I/O errors, by running > sudo dd of=/sys/module/firewire_ohci/parameters/debug <<< 2 > before you attach the Freecom Quattro, then reproduce the I/O errors. > > Lastly, if you have the means to compile C programs on this laptop, it > would interesting to see the output of the program > lsfirewirephy > from https://code.google.com/p/jujuutils/. > |
From: Clemens L. <cl...@la...> - 2014-01-19 17:08:09
|
pho...@ya... wrote: > Could you recommend some very good firewire cables, a certain > manufacturer maybe so that I could eliminate that potential problem? I > currently got the cables supplied with the freecom and western digital > drives, plus some from reichelt.de and some new delock ones bought from > amazon. I don't know where the device manufacturers get their cheap junk (although shorter cables actually are more handy), but any separately bought cable should work fine ... > They all work fine with the older freecom drives, but not with > the new 4tb freecom drive. ... especially if they work somewhere else. (FireWire connectors are constructed so that only the cables wear out.) > On this google code webpage https://code.google.com/p/jujuutils/ is this > requirement "package requires the new "Juju" FireWire stack.". Does the > new kernel use that juju firewire stack ? Yes. (It says so right on that page. Now. ;-) Regards, Clemens |