lkml.org 
[lkml]   [2010]   [Dec]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Issue with firewire from 2.6.35.9 to 2.6.36.1
    Stefan Richter wrote:
    > > On Sun, 2010-12-05 at 17:37 -0600, Robin Cook wrote:
    > > > I recently upgraded from 26.35.9 to 2.6.36.1 and now the /dev/fwX
    > > > devices are not being created. I have udev 164 installed.
    > > >
    > > > 2.6.35.9 dmesg firewire lines...
    > > >
    > > > firewire_ohci 0000:07:00.0: PCI INT A -> GSI 44 (level, low) -> IRQ 44
    > > > firewire_ohci 0000:07:00.0: setting latency timer to 64
    > > > firewire_ohci: Added fw-ohci device 0000:07:00.0, OHCI v1.10, 4 IR + 8 IT contexts, quirks 0x1
    > > > firewire_core: created device fw0: GUID 0010dc0001adc862, S400
    > > > firewire_core: created device fw1: GUID 00808803072803a5, S100
    > > > firewire_core: phy config: card 0, new root=ffc1, gap_count=5
    > > >
    > > > 2.6.36.1 dmesg firewire lines...
    > > >
    > > > firewire_ohci 0000:07:00.0: PCI INT A -> GSI 44 (level, low) -> IRQ 44
    > > > firewire_ohci 0000:07:00.0: setting latency timer to 64
    > > > firewire_ohci 0000:07:00.0: irq 75 for MSI/MSI-X
    > > > firewire_ohci: Added fw-ohci device 0000:07:00.0, OHCI v1.10, 4 IR + 8 IT contexts, quirks 0x1
    >
    > ... Rather, MSI support
    > (messages signaled interrupts, added to firewire-ohci in kernel 2.6.36)
    > of your controller might be buggy.

    I'd guess if you check in /proc/interrupts you see that no interrupts
    have arrived for IRQ 75 (firewire-ohci).

    > Which controller do you have according to "lspci -nn"?

    "0010DC" is MSI. I've heard about VT6315 and JMB381 controllers on
    their mainboards; since the driver tries to enable MSI, it must be the
    VT6315.


    Regards,
    Clemens


    \
     
     \ /
      Last update: 2010-12-06 10:41    [W:0.023 / U:0.156 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site