lkml.org 
[lkml]   [2010]   [Jul]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: 2.6.35-rc6 to 2.6.32.16: JuJu firewire issues
    Hi Stefan,
    thank you for your care of this issue. I have just returned the crappy
    IcyBOX IB-250StUE-B back to the reseller. On the circuit board there was
    Apr 2008 timestamp (regarding the JMicron JMB 353 chip doing the SATA to
    FireWire 1394a + USB 2.0 conversion).

    I tried in the morning to connect the IcyBox to this laptops internal
    Ricoh Co Ltd R5C552 IEEE 1394 Controller but had issues to power-up the drive
    at all. Not even using USB hub to supply power to it. I connected it to
    the ricoh chip via a 6 to 4 pin cable but also tried the not very good
    Kouwell 7004 PCMCIA card (which does not supply enough power unless I
    buy external, optional power supply of unknown specs and plug it into the
    PCMCIA card).

    Many thanks for your care,
    Martin
    P.S.: Yes, laptop (computer B) is a single-core, old P4-M computer with ICH3
    chipset.

    Stefan Richter wrote:
    > Stefan Richter wrote:
    >> Martin Mokrejs wrote at LKML:
    >>> Hi Jay,
    >>> Jay Fenlason wrote:
    >>>> On Fri, Jul 23, 2010 at 04:09:21PM +0200, Martin Mokrejs wrote:
    >>>>> Hi,
    >>>>> I bought a external harddrive with firewire and USB interfaces (IcyBOX IB-250StUE-B).
    >>>>> If I connect it to a desktop computer A I get kernel crash during boot (see
    >>>>> both attached dmesg-*.txt files).
    >>
    >> The crash which you reported is in sbp2 (of the old ieee1394 stack alias
    >> linux1394, not in firewire-sbp2 (of the new firewire stack alias juju).
    >
    > I have logged your report as
    > https://bugzilla.kernel.org/show_bug.cgi?id=16452
    > nodemgr, sbp2: NULL pointer dereference in sbp2_update
    > but set its status to WILL_NOT_FIX for now.
    >
    > The bug seems to be in the nodemgr component of the ieee1394 core
    > driver. This is one of the things that were rewritten from scratch in
    > firewire-core with a fundamentally different implementation, for good
    > reasons.
    >
    > Perhaps somebody else wants to look into a possible fix for this bug,
    > but this seems very unlikely. (Basically, a bug fix already exists in
    > the form of firewire-core.)


    \
     
     \ /
      Last update: 2010-07-24 14:05    [W:0.023 / U:31.160 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site