Re: half a loop
Brought to you by:
aeb,
bencollins
From: Stefan R. <st...@s5...> - 2011-12-19 21:25:33
|
On Dec 19 Carl Karsten wrote: > On Dec 19 Carl Karsten wrote: > > On Mon, Dec 19, 2011 at 12:20 PM, Carl Karsten > > <ca...@pe...> wrote: > > > On Sun, Dec 18, 2011 at 7:57 AM, Stefan Richter > > > <st...@s5...> wrote: > > >> Furthermore, tell us whether you end up with two or three /dev/fw* > > >> again (i.e. whether neither node succeeded to probe the other, or > > >> one of them succeeded to probe the other). Then, run either > > >> gscanbus or firecontrol on _each_ "port" and use it to trigger a > > >> bus reset, then watch if this results in all four expected /dev/fw* > > >> becoming available. > > > > juser@pc8:~$ ls /dev/fw? > > /dev/fw0 /dev/fw1 /dev/fw2 > > > > juser@pc8:~/firecontrol$ sudo ./firecontrol 0 > > firecontrol trunk_20111218 > > Copyright (C) 2002-2007 by Manfred Weihs <mw...@us...> > > This software comes with absolutely no warranty. > > > > successfully got handle > > current generation number (driver): 0 > > 2 card(s) found > > nodes on bus: 2, card name: /dev/fw2 > > nodes on bus: 2, card name: /dev/fw0 > > using adapter 0 > > found: 2 nodes on bus, local ID is 0, IRM is 1 > > current generation number (adapter): 2 > > > > entering command mode > > Type 'help' for more information! > > Command: br > > successfully reset the bus (long bus reset) > > Command: > > bus reset occurred. > > new generation number: 3, 2 nodes on the bus, local ID: 0 > > > > juser@pc8:~/firecontrol$ ls /dev/fw? > > /dev/fw0 /dev/fw1 /dev/fw2 /dev/fw3 So sometimes the new node probe after a bus reset is successful... > I rebooted, no connections came up. firecontrol on both, br, still no > connections. > > juser@pc8:~/firecontrol$ sudo ./firecontrol 1 > firecontrol trunk_20111218 > Copyright (C) 2002-2007 by Manfred Weihs <mw...@us...> > This software comes with absolutely no warranty. > > successfully got handle > current generation number (driver): 0 > 2 card(s) found > nodes on bus: 2, card name: /dev/fw1 > nodes on bus: 2, card name: /dev/fw0 > using adapter 1 > found: 2 nodes on bus, local ID is 0, IRM is 1 > current generation number (adapter): 3 > > entering command mode > Type 'help' for more information! > Command: br > successfully reset the bus (long bus reset) > Command: > bus reset occurred. > new generation number: 4, 2 nodes on the bus, local ID: 0 > > juser@pc8:~$ ls /dev/fw? > /dev/fw0 /dev/fw1 ...but other times not. In other words, neither going from the initial gap count of 63 to the optimized gap count of 5 nor any other effects that the subsequent bus resets might have do get things going in any systematic manner. -- Stefan Richter -=====-==-== ==-- =--== http://arcgraph.de/sr/ |