Re: Issue with firewire from 2.6.35.9 to 2.6.36.1

[Maxim Levitsky]

On Sun, 2010-12-05 at 17:37 -0600, Robin Cook wrote:
> Hello,
> 
> 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
> 
> I have compared the difference between the two kernel configs and the
> only differences that I see that may apply to the firewire are:
> 
>  CONFIG_DNOTIFY=y
> -CONFIG_INOTIFY=y
>  CONFIG_INOTIFY_USER=y
> 
>  # CONFIG_IEEE1394 is not set 
> +CONFIG_FIREWIRE_NOSY=m  
>  CONFIG_I2O=m
> 
> On the ieee1394 wiki page it says that these kernel option are expected
> to be on for the libraw1394:
> 
> CONFIG_INOTIFY=y
> CONFIG_INOTIFY_USER=y
> CONFIG_EPOLL=y
> 
> These option are correct in the 2.6.35.9 kernel but the CONFIG_INOTIFY
> option is missing completely in the 2.6.36.1 kernel.
> 
> Is this a change in how the firewire works in the kernel and that udev
> needs to be modified or is there something else wrong?

CC'ed linux1394-devel

It looks like now firewire stack doesn't discover any devices?
I don't think its Kconfig issue.

Best regards,
	Maxim Levitsky


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/