http://bugzilla.novell.com/show_bug.cgi?id=586172 http://bugzilla.novell.com/show_bug.cgi?id=586172#c11 --- Comment #11 from Stefan Richter <stefan-r-nvbz@s5r6.in-berlin.de> 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.