linux-kernel - Re: Issue with firewire from 2.6.35.9 to 2.6.36.1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 06 Dec 2010 16:04:47 -0600
From:	Robin Cook <rcook@...ms.net>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	Maxim Levitsky <maximlevitsky@...il.com>,
	linux-kernel@...r.kernel.org,
	linux1394-devel <linux1394-devel@...ts.sourceforge.net>
Subject: Re: Issue with firewire from 2.6.35.9 to 2.6.36.1

On Mon, 2010-12-06 at 08:29 +0100, Stefan Richter wrote:
> > 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?
> 
> I hadn't noticed that the INOTIFY kconfig options changed relative to
> what is documented at the wiki.  I'll update that.
> 
> It is most likely not the cause for your issue.  Rather, MSI support
> (messages signaled interrupts, added to firewire-ohci in kernel 2.6.36)
> of your controller might be buggy.  Which controller do you have
> according to "lspci -nn"?
> 
> Try "modprobe -r firewire-ohci", "modprobe firewire-ohci quirks=17".
> The unrelated quirks flag 1 is already present in firewire-ohci's
> quirks list; the additional flag 16 switches off MSI.

Output from lspci -nn on the firewire controller.

07:00.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6315 Series Firewire Controller [1106:3403]

The modprobe firewire-ohci quirks=17 worked to get the devices being
created again.



Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)