RE: Linux 1394 somewhat unfriendly during boot?
Brought to you by:
aeb,
bencollins
From: Mark K. <mk...@co...> - 2000-05-19 22:22:28
|
Manfred, Thanks for the info. There's some good stuff there. I think one important point you make is the compile option - kernel vs. modules. I am compiled into the kernel and that means the loading of the driver stack is earlier. I could certainly take it out, but I think in the end it is not practical to have end-user types doing insmod's. I know, 'cause I'm an in user type and I don't know how to do it!! I may make a version of the kernel with module based loading this weekend. Could you send back the instructions for doing the insmod steps so that I get it right? I agree that some of the stability problem seems more apparent when I build larger topologies. I intend to look into this more later. I am also seeing inconsistent identification of devices. Sometimes the GUID's show up, sometimes they don't. I'd like to get my hands on a real analyzer (3A or something) but they are too expensive for play. I understood that there used to be some TI software for doing this with PCI-Lynx. Is anyone in possession of that? More later, I'm sure. Thanks, Mark -----Original Message----- From: Manfred Weihs [mailto:e95...@st...] Sent: Friday, May 19, 2000 11:12 AM To: lin...@li... Subject: Re: Linux 1394 somewhat unfriendly during boot? Mark Knecht wrote: > This seems like the Linux 1394 system may be pumping a lot of either packets > onto the bus, or doing a lot of bus resets. I also observed, that when booting my linux PC (and since I compiled 1394 into the kernel, not into modules, the subsystem is loaded during bootup) several bus resets occur. I do not know if this is bad or unfriendly (the design of 1394 allows bus resets anytime, so it should not hurt, if there are several bus resets), but I think one bus reset should be enough. I more frequently observed problems in the other direction, that activities of other nodes caused my linux to crash. For example we have 1394-evaluation-boards from Vitana in our 1394-network, and if we press the reset-button on this boards, my Linux pc sometimes dies (either completly hangs up, so that I am not even able to ping it, or it starts a reboot, or during reboot [mostly during fscheck since this takes some time] gets a kernel panic). BTW: The Win boxes also die sometimes, but my linux box does so more frequently. I am sorry, that I was not yet able to find out, what conditions must exactly be fulfilled to cause such a crash, so I cannot always reproduce it (that is the reason why I did not yet post a bug report to the list); but it seems that the instability grows with the number of active nodes in the network. I am not sure, if this is caused by a problem of the hardware (Unibrain card) or the lowlevel driver (pcilynx) or by the higher subsystem layers. But I think that it is rather a software than a hardware problem, because I yesterday tried to press the reset-button of that Vitana-board many times during bootup and linux hang up _after_ the 1394-driver was loaded. Manfred Weihs _______________________________________________ mailing list lin...@li... http://lists.sourceforge.net/mailman/listinfo/linux1394-devel |