http://bugzilla.novell.com/show_bug.cgi?id=586172 http://bugzilla.novell.com/show_bug.cgi?id=586172#c2 Jon Schewe changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|jpschewe@mtu.net | --- Comment #2 from Jon Schewe 2010-03-09 13:38:27 UTC --- Still doesn't work: <7>[ 14.684363] HDA Intel 0000:00:10.1: irq 27 for MSI/MSI-X <7>[ 14.684388] HDA Intel 0000:00:10.1: setting latency timer to 64 <6>[ 14.704064] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[19] MMIO=[febff800-febfffff] Max Packet=[1024] IR/IT contexts=[4/8] <7>[ 16.104626] ieee1394: Node added: ID:BUS[0-00:1023] GUID[0090a976213be423] <7>[ 16.104707] ieee1394: Host added: ID:BUS[0-01:1023] GUID[0010dc0000cf92b6] <6>[ 16.300598] scsi6 : SBP-2 IEEE-1394 <4>[ 17.752021] ALSA hda_intel.c:709: azx_get_response timeout, switching to polling mode: last cmd=0x000f0001 <6>[ 18.308995] hda_codec: ALC880: BIOS auto-probing. <7>[ 18.327711] ALSA hda_codec.c:4284: autoconfig: line_outs=4 (0x14/0x16/0x15/0x17/0x0) <7>[ 18.327715] ALSA hda_codec.c:4288: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) <7>[ 18.327718] ALSA hda_codec.c:4292: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) <7>[ 18.327721] ALSA hda_codec.c:4293: mono: mono_out=0x0 <7>[ 18.327723] ALSA hda_codec.c:4296: dig-out=0x1e/0x0 <7>[ 18.327725] ALSA hda_codec.c:4304: inputs: mic=0x18, fmic=0x19, line=0x1a, fline=0x0, cd=0x1c, aux=0x0 <7>[ 18.327729] ALSA hda_codec.c:4306: dig-in=0x1f <7>[ 18.576024] ALSA patch_realtek.c:1309: realtek: Enabling init ASM_ID=0xe603 CODEC_ID=10ec0880 <6>[ 20.497777] ieee1394: sbp2: Logged into SBP-2 device <6>[ 20.527761] ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [1024] <5>[ 20.658321] scsi 6:0:0:0: Direct-Access WD My Book 1025 PQ: 0 ANSI: 4 <5>[ 20.677398] sd 6:0:0:0: Attached scsi generic sg2 type 0 <6>[ 20.696384] scsi7 : SBP-2 IEEE-1394 <5>[ 20.718961] sd 6:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB) <5>[ 20.765558] sd 6:0:0:0: [sdb] Write Protect is off <7>[ 20.783941] sd 6:0:0:0: [sdb] Mode Sense: 10 00 00 00 <5>[ 20.802643] sd 6:0:0:0: [sdb] Cache data unavailable <3>[ 20.820871] sd 6:0:0:0: [sdb] Assuming drive cache: write through <5>[ 20.923004] sd 6:0:0:0: [sdb] Cache data unavailable <3>[ 20.941037] sd 6:0:0:0: [sdb] Assuming drive cache: write through <6>[ 20.959105] sdb: sdb1 <5>[ 21.608265] sd 6:0:0:0: [sdb] Cache data unavailable <3>[ 21.626210] sd 6:0:0:0: [sdb] Assuming drive cache: write through <5>[ 21.644167] sd 6:0:0:0: [sdb] Attached SCSI disk <6>[ 24.840511] ieee1394: sbp2: Logged into SBP-2 device <6>[ 24.870753] ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [1024] <5>[ 25.007329] scsi 7:0:1:0: Enclosure WD My Book Device PQ: 0 ANSI: 4 <5>[ 25.026048] scsi 7:0:1:0: Attached scsi generic sg3 type 13 <4>[ 25.044466] ------------[ cut here ]------------ <4>[ 25.062376] WARNING: at /usr/src/packages/BUILD/kernel-vanilla-2.6.33/linux-2.6.33/fs/sysfs/dir.c:487 sysfs_add_one+0xc9/0x130() <4>[ 25.080659] Hardware name: MS-7207PV <4>[ 25.098624] sysfs: cannot create duplicate filename '/bus/ieee1394/drivers/sbp2/0090a976213be423-1' <4>[ 25.116785] Modules linked in: snd_hda_codec_realtek sbp2 snd_hda_intel ppdev ohci1394 snd_hda_codec snd_hwdep amd64_edac_mod parport_pc edac_core snd_pcm parport sr_mod ieee1394 k8temp pcspkr edac_mce_amd i2c_nforce2 snd_timer button forcedeth cdrom floppy snd soundcore sg snd_page_alloc usbhid linear raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid0 ohci_hcd ssb mmc_core ehci_hcd pcmcia pcmcia_core sd_mod usbcore dm_snapshot dm_mirror dm_region_hash dm_log reiserfs aic7xxx scsi_transport_spi edd dm_mod raid1 fan ata_generic sata_nv pata_amd libata scsi_mod thermal processor thermal_sys <4>[ 25.194769] Pid: 756, comm: knodemgrd_0 Not tainted 2.6.33-29-vanilla #1 <4>[ 25.214696] Call Trace: <4>[ 25.234279] [<ffffffff81050d18>] warn_slowpath_common+0x78/0xb0 <4>[ 25.254077] [<ffffffff81050dac>] warn_slowpath_fmt+0x3c/0x40 <4>[ 25.273819] [<ffffffff8118a789>] sysfs_add_one+0xc9/0x130 <4>[ 25.293416] [<ffffffff8118ac6b>] sysfs_do_create_link+0x11b/0x160 <4>[ 25.312828] [<ffffffff8118acce>] sysfs_create_link+0xe/0x10 <4>[ 25.332005] [<ffffffff812d265e>] driver_sysfs_add+0x2e/0x90 <4>[ 25.350993] [<ffffffff813e49a4>] ? __down+0x74/0xb0 <4>[ 25.369792] [<ffffffff812d2b31>] device_bind_driver+0x11/0x30 <4>[ 25.388486] [<ffffffff812d2b8b>] device_attach+0x3b/0xa0 <4>[ 25.406960] [<ffffffff812d1190>] ? bus_rescan_devices_helper+0x0/0x70 <4>[ 25.425411] [<ffffffff812d11d9>] bus_rescan_devices_helper+0x49/0x70 <4>[ 25.443764] [<ffffffff812d1ae8>] bus_for_each_dev+0x68/0x90 <4>[ 25.462014] [<ffffffff812d1b24>] bus_rescan_devices+0x14/0x20 <4>[ 25.480096] [<ffffffffa03b2da9>] nodemgr_host_thread+0x289/0x360 [ieee1394] <4>[ 25.498208] [<ffffffffa03b2b20>] ? nodemgr_host_thread+0x0/0x360 [ieee1394] <4>[ 25.516206] [<ffffffff8106f4ce>] kthread+0x8e/0xa0 <4>[ 25.534116] [<ffffffff81003cb4>] kernel_thread_helper+0x4/0x10 <4>[ 25.552056] [<ffffffff8106f440>] ? kthread+0x0/0xa0 <4>[ 25.569918] [<ffffffff81003cb0>] ? kernel_thread_helper+0x0/0x10 <4>[ 25.587762] ---[ end trace f14e7ebc54e1849c ]--- <5>[ 25.632528] ses 7:0:1:0: Attached Enclosure device -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=586172 http://bugzilla.novell.com/show_bug.cgi?id=586172#c4 Jon Schewe changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|WORKSFORME | --- Comment #4 from Jon Schewe 2010-04-18 21:31:25 UTC --- I spoke too soon. The first boot didn't cause the error, but subsequent boots did (both warm reboot and cold reboot). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=586172 http://bugzilla.novell.com/show_bug.cgi?id=586172#c6 --- Comment #6 from Jon Schewe 2010-04-25 15:04:19 UTC --- This disk does not have a button on it. It is just a disk. It doesn't appear that the new drivers are present: jpschewe@jon:/lib/modules/2.6.31.12-0.2-default

find . -name firewire-ohci.ko -print

-- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=586172 http://bugzilla.novell.com/show_bug.cgi?id=586172#c8 --- Comment #8 from Jon Schewe 2010-04-25 16:52:08 UTC --- (In reply to comment #7)

...

This disk does not have a button on it. It is just a disk.

Ah, right, the MyBook. I guess the Enclosure logical unit is for the status LEDs that are used as a capacity indicator under other OSs.

There is only 1 LED on the front that flashes with activity. No capacity indication.

If you are willing to spend the effort to narrow down what the ieee1394 driver is doing wrong, you could get me some device data in one of the following two ways:

/1./ Install a kernel that has new driver stack enabled, and attach the file /sys/bus/firewire/devices/fw1/config_rom here. It is a binary file.

The 1 in this path assumes that the host was discovered before the disk. (host: fw0, disk: fw1, units on the disk: fw1.0 and fw1.1)

Not likely to get this unless there already is one packaged for opensuse.

/2./ Install the tool firecontrol (http://firecontrol.sourceforge.net/, formerly known as 1394commander, if neither firecontrol nor 1394commander is not packaged for SuSE, install the devel version of libraw1394 and compile firecontrol), then run { for i in {4,5,6,7}{0,1,2,3,4,5,6,7,8,9,a,b,c,d,e,f}{0,4,8,c}; do echo "r . 0 0xfffff0000$i 4"; done } | firecontrol > log and attach the log here.

The 0 after r . in the command string assumes that the disk was discovered as node ID:BUS[0-00:1023] whereas the host is ID:BUS[0-01:1023]. Tried this, but got lots of "insufficient arguments for operation!" And the log is full of: Command: 0xfffff000064c 4 illegal command! Command: r . 0

Will attach -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=586172 http://bugzilla.novell.com/show_bug.cgi?id=586172#c10 Jon Schewe changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #356677|0 |1 is obsolete| | --- Comment #10 from Jon Schewe 2010-04-25 16:56:58 UTC --- Created an attachment (id=356678) --> (http://bugzilla.novell.com/attachment.cgi?id=356678) logfile Ahh, found the error, I had a line break in there from the copy/paste. The disk is my only firewire device attached, so I assumed the 0 to be correct. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=586172 http://bugzilla.novell.com/show_bug.cgi?id=586172#c11 --- Comment #11 from Stefan Richter 2010-04-25 22:06:53 UTC --- Created an attachment (id=356688) --> (http://bugzilla.novell.com/attachment.cgi?id=356688) Jon's logfile pretty-printed Attached: the data from attachment 356678 parsed and pretty-printed. As far as I can see, the configuration ROM is organized the same way as with the dual-unit devices which I have. First I thought I could not reproduce the bug, but now I tried loading the drivers with respective dual-unit devices already attached (in contrast to first loading the drivers, then plugging the device(s) in). Obviously the nodemgr gets himself into trouble if it deals with dual-unit devices during its own startup. I'll see what I can find out about the cause. It may take a while though because the severity of the bug isn't high AFAICS, and the ieee1394 drivers are in minimum maintenance mode now since work is concentrated on the newer firewire drivers now.

...

...

This disk does not have a button on it. It is just a disk.

Ah, right, the MyBook. I guess the Enclosure logical unit is for the status LEDs that are used as a capacity indicator under other OSs.

There is only 1 LED on the front that flashes with activity. No capacity indication.

Strange then that there is another logical unit at all. Still, it shouldn't matter to ieee1394, it should create 0090a976213be423-0 and 0090a976213be423-1 once but not attempt to repeat the latter. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=586172 http://bugzilla.novell.com/show_bug.cgi?id=586172#c13 --- Comment #13 from Stefan Richter 2010-04-25 23:32:41 UTC ---

I'm going to enable CONFIG_FIREWIRE for the Factory kernel. Should the old stack be enabled at all?

By now, the new drivers support all of the hardware that the old drivers support, except for the moderately rare (and no longer produced) ALi PCI-FireWire controllers and the extremely rare NForce2 (which don't fully workwith the old stack either) and AFAIK the rare and ancient Apple UniNorth v1 controllers. Still, since Fedora has been the only distribution to ship the new drivers until recently, it may make sense to install the old drivers too as a fallback for unforeseen issues. Hard to say whether such a parallel installation or a single-stack installation will result in least support issues. The drivers as well as the low-level libraries libraw1394 and libdc1394 are fit to work seamlessly either way.

What enforces that the firewire modules are higher priority?

The way the kernel's makefiles are ordered, the driver core will first attempt to bind firewire-ohci before ohci1394 if both have been loaded into the kernel or statically linked into the kernel. A modular build together with shipped modprobe blacklist entries as listed at https://ieee1394.wiki.kernel.org/index.php/Juju_Migration#How_to_suppress_au... gives explicit control though. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=586172 http://bugzilla.novell.com/show_bug.cgi?id=586172#c15 Stefan Richter changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.kernel.org | |/show_bug.cgi?id=15853 --- Comment #15 from Stefan Richter 2010-04-26 01:24:59 UTC --- Tracked as upstream bug at kernel.org now, #15853. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=586172 http://bugzilla.novell.com/show_bug.cgi?id=586172#c17 --- Comment #17 from Michal Marek 2010-04-26 09:16:39 UTC --- (In reply to comment #14)

Michal, can you add the blacklist entries? Do we have a way of doing that on a per-kernel basis so we don't break 11.2 installations using 11.3M kernels in the interim?

Do we really need this? Since we have modules.order support in module-init-tools, module priority should follow the makefile order. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=586172 https://bugzilla.novell.com/show_bug.cgi?id=586172#c19 --- Comment #19 from Stefan Richter 2010-09-12 09:23:41 UTC --- At upstream (https://bugzilla.kernel.org/show_bug.cgi?id=15853) there will be no attempt to fix this. The ieee1394 subsystem is planned to be removed from the kernel at 2.6.37. The problem does not exist in its replacement, the firewire subsystem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

<4>[ 21.594754] Modules linked in: snd_hda_codec_realtek sbp2 snd_hda_intel firewire_ohci firewire_core snd_hda_codec ppdev amd64_edac_mod crc_itu_t sr_mod ^^^^^^^^^^^^^ This is the new module, right? parport_pc snd_hwdep cdrom parport edac_core snd_pcm i2c_nforce2 sg forcedeth ohci1394 ^^^^^^^^ And this is the obsolete one? It looks like the the obsolete module gets loaded first (the module list is single linked, so the last module is the head of the

https://bugzilla.novell.com/show_bug.cgi?id=586172 https://bugzilla.novell.com/show_bug.cgi?id=586172#c21 --- Comment #21 from Michal Marek 2010-09-13 10:01:34 UTC --- (In reply to comment #18) list), this is strange... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=586172 https://bugzilla.novell.com/show_bug.cgi?id=586172#c23 --- Comment #23 from Stefan Richter 2010-09-13 18:38:29 UTC --- In case of a dual stack installation, autoloading of the modules can be controlled thus: https://ieee1394.wiki.kernel.org/index.php/Juju_Migration#How_to_suppress_au... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=586172 https://bugzilla.novell.com/show_bug.cgi?id=586172#c25 --- Comment #25 from Jon Schewe 2010-09-14 10:55:20 UTC --- (In reply to comment #23)

In case of a dual stack installation, autoloading of the modules can be controlled thus: https://ieee1394.wiki.kernel.org/index.php/Juju_Migration#How_to_suppress_au...

I just rebooted with these blacklist settings and the error didn't appear on this reboot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=586172 https://bugzilla.novell.com/show_bug.cgi?id=586172#c Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |mmarek@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=586172 http://bugzilla.novell.com/show_bug.cgi?id=586172#c28 --- Comment #28 from Bernhard Wiedemann --- This is an autogenerated message for OBS integration: This bug (586172) was mentioned in https://build.opensuse.org/request/show/39554 Factory / kernel-source -- You are receiving this mail because: You are on the CC list for the bug.