[lkml]   [2006]   [Oct]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Subjectohci1394 regression in 2.6.19-rc1 (was Re: Merge window closed: v2.6.19-rc1)
    Alistair John Strachan wrote:
    > Booted fine here, but I've got a few strange messages from the firewire
    > subsystem that weren't present in 2.6.18. I think it marginally slows down
    > boot up, but I could just be imagining it.
    > [alistair] 16:04 [~] dmesg | grep 1394
    > ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[19] MMIO=[dffff000-dffff7ff] Max Packet=[2048] IR/IT contexts=[4/8]
    > ohci1394: fw-host1: OHCI-1394 1.1 (PCI): IRQ=[17] MMIO=[dfffc000-dfffc7ff] Max Packet=[2048] IR/IT contexts=[4/8]
    > ohci1394: fw-host0: Running dma failed because Node ID is not valid
    > ohci1394: fw-host0: AT dma reset ctx=0, aborting transmission
    > ieee1394: Current remote IRM is not 1394a-2000 compliant, resetting...
    > ieee1394: Host added: ID:BUS[0-00:1023] GUID[00023c0091023fd7]
    > ieee1394: Host added: ID:BUS[1-00:1023] GUID[000129200003d023]

    Thanks for the quick report. Could you please test the following, each
    one separately?


    B. Revert patch "Initialize ieee1394 early when built in";a=commitdiff_plain;h=8df4083c5291b3647e0381d3c69ab2196f5dd3b7

    I don't see how any other ohci1394 patch after 2.6.18 could lead up to
    that message. I also don't understand what causes this glitch. At least
    it seems recoverable, according to the "Host added" lines.
    Stefan Richter
    -=====-=-==- =-=- --=-=
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-10-05 21:01    [W:0.042 / U:7.160 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site