[Bug 529524] [NEW] Impossible to activate the new firewire kernel stack on Karmic

Sun Feb 28 16:30:21 UTC 2010

Public bug reported:

I have posted a thread on the Ubuntu forums but as I did not get any
answer, it is probably a bug, and not my own mistake. This bug is
related to Bug #276463 which purpose was to provide both old and new
stack on Ubuntu but still defaulting to the old one. This current bug
report is stating that eventhough the new stack is also provided, it is
not possible to activate it.

Here is what I reported back a few weeks ago in the forums (http://ubuntuforums.org/showthread.php?t=1389329):
As the new firewire kernel stack is not experimental since kernel 2.6.31 (the version on Karmic), I thought about giving it a try.
I've checked the official stack migration wiki (http://ieee1394.wiki.kernel.org/index.php/Juju_Migration) and did what was recommended there. As Ubuntu shipped with both the old and new stack but with the new one disabled in /etc/modprobe.d/blacklist-firewire.conf
Therefore, I've modified this last file so that it looks like this now:
blacklist ohci1394
blacklist sbp2
blacklist dv1394
blacklist raw1394
blacklist video1394

#blacklist firewire-ohci
#blacklist firewire-sbp2

So the old ieee1394 stack is blacklisted and the new firewire stack
should be automatically loaded.

I have rebooted my computer so changes take effect and I've performed an lsmod which did not display the expected result
Module                  Size  Used by
firewire_sbp2          15112  0 
firewire_core          47296  1 firewire_sbp2
crc_itu_t               1852  2 rt61pci,firewire_core
sbp2                   22888  1 
ohci1394               29900  1 
ieee1394               86596  2 sbp2,ohci1394

As you can see the firewire_sbp2 is unused, whereas the sbp2 (the old stack) is used (I have an external firewire hard drive plugged in). If I plug out my HD, then the sbp2 gets also unused. Thus, it is the one used for the HD. And as you can see from the dependency sbp2 is based on the old stack which I had blacklisted.
Side note: I have unplugged my HD, then using 'modprobe -r' I removed the sbp2 and ohci1394 modules. Then, I plugged back my HD hoping that the new stack would be used... No success. Linux did not even see that I had plugged back my HD, as you can see in the dmesg output below, which only shows the device and modules removal:
[  268.610021] sd 6:0:1:0: [sdc] Stopping disk
[  268.650880] ieee1394: sbp2: Logged out of SBP-2 device
[  304.998148] ieee1394: Node removed: ID:BUS[0-00:1023]  GUID[0090a991e0107124]
[  304.998375] ieee1394: Node removed: ID:BUS[0-01:1023]  GUID[0010dc00006c3bb8]

As I have followed the migration guide and blacklisted the old stack, I
was expecting the new stack to be operationnal. However, the old one is
still the one operationnal and eventhough the new one is "loaded" it is
not used.

Updated: I have tested it with the latest Karmic update and when I activate the new stack and restart the computer, the behaviour is slightly different now than a few weeks ago. Here is the output of the lsmod:
Module                  Size  Used by
firewire_sbp2          15272  0 
firewire_core          47392  1 firewire_sbp2
crc_itu_t               1852  1 firewire_core
ohci1394               30220  0 
ieee1394               86628  1 ohci1394

For information, the firewire drive was plugged in, but no module where loaded, so I could not access it. Here is a more interesting output from dmesg, this time Linux detects that I plug the drive out and in, but nothing more is happening.
[  166.241229] ieee1394: Node changed: 0-01:1023 -> 0-00:1023
[  166.241244] ieee1394: Node paused: ID:BUS[0-00:1023]  GUID[0090a991e0107124]
[  169.300088] ieee1394: Node removed: ID:BUS[0-00:1023]  GUID[0090a991e0107124]
[  171.380328] ieee1394: The root node is not cycle master capable; selecting a new root node and resetting...
[  171.655903] ieee1394: Node added: ID:BUS[0-00:1023]  GUID[0090a991e0107124]
[  171.658338] ieee1394: Node changed: 0-00:1023 -> 0-01:1023

ProblemType: Bug
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC0:  jean-christophe   2345 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfc020000 irq 17'
   Mixer name	: 'Conexant CX20561 (Hermosa)'
   Components	: 'HDA:14f15051,17aa2100,00100000'
   Controls      : 14
   Simple ctrls  : 7
Date: Sun Feb 28 17:24:09 2010
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=9c8acd99-53cc-497d-a89e-3a3142ae8716
MachineType: LENOVO 2241BN5
Package: linux-image-2.6.31-19-generic-pae 2.6.31-19.56
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=UUID=66ce5f80-3e6d-40af-a6e0-a678ba8e7383 ro quiet splash  crashkernel=384M-2G:64M,2G-:128M
ProcEnviron:
 LANGUAGE=en_GB.UTF-8
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic-pae
RelatedPackageVersions:
 linux-backports-modules-2.6.31-19-generic-pae N/A
 linux-firmware 1.26
RfKill:
 0: phy0: Wireless LAN
 	Soft blocked: no
 	Hard blocked: no
SourcePackage: linux
Uname: Linux 2.6.31-19-generic-pae i686
WpaSupplicantLog:

XsessionErrors:
 (gnome-settings-daemon:2466): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:2613): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:2630): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-panel:2612): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window
dmi.bios.date: 11/26/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 6FET82WW (3.12 )
dmi.board.name: 2241BN5
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: FR500089
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6FET82WW(3.12):bd11/26/2009:svnLENOVO:pn2241BN5:pvrThinkPadT500:rvnLENOVO:rn2241BN5:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2241BN5
dmi.product.version: ThinkPad T500
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

** Tags: firewire ieee1394 kernel stack

-- 
Impossible to activate the new firewire kernel stack on Karmic
https://bugs.launchpad.net/bugs/529524
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.