Hi John,<br>Yeah, i still have mesh crashing on me every now and then. Its a hit and miss with two antennas plugged in.<br>I haven't had problem with it in the past day or so but i wont be surprised if it crashed right after i send this email.<br>
<br>What was the change made in the driver? Is there a new one out that i should update to?<br>thanks for your help.<br><br>-Sulochan<br><br><div class="gmail_quote">On Sat, Mar 1, 2008 at 9:14 AM, John Watlington <<a href="mailto:wad@laptop.org">wad@laptop.org</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Sorry it took so long to get back to you on this. It's been a rough<br>
week.<br>
Are you still having problems ?<br>
<br>
Does the same think happen when you attach the antennas after the<br>
server is booted ? Take a look at dmesg after doing this.<br>
<br>
I'm having trouble<br>
<br>
The tx_watchdog timeouts are due to problems in the<br>
Marvell firmware/hardware. A rewrite of the driver stopped this<br>
problem from crashing the driver, but the underlying problem is still<br>
happening.<br>
<br>
Regards,<br>
<font color="#888888">John<br>
</font><div><div></div><div class="Wj3C7c"><br>
On Feb 18, 2008, at 10:56 PM, sulochan acharya wrote:<br>
<br>
> Hi John,<br>
> Both the antennas are using firmware version 31.07, and they work<br>
> fine separately, but i cant get them to behave<br>
> when both are connected to the XS. In fact if i boot the machine<br>
> with two antennas connected it takes a long time to get to<br>
> the point where it checks for the msh.<br>
> Can it be a problem with the XS?<br>
><br>
> I was able to get both to work for a short period of time<br>
> yesterday, but a network restart got me back to the same error<br>
> messages, and same problem. I did not reprogram the antennas<br>
> because both are actually working fine. It this problem same to<br>
> antenna going to repeater mode, i check the track for this error,<br>
> but didn't find something that matches this exact problem.<br>
><br>
> Anyone with any knowledge on this please help.<br>
><br>
> thanks,<br>
><br>
> -Sulochan<br>
><br>
> On Feb 15, 2008 8:25 PM, John Watlington <<a href="mailto:wad@laptop.org">wad@laptop.org</a>> wrote:<br>
><br>
> Those messages are certainly from the driver, but it has been tested<br>
> and works fine with multiple antenna. The most likely source of this<br>
> problem is old firmware in the second antenna. Please take a look<br>
> at:<br>
> <a href="http://wiki.laptop.org/go/Active_Antenna_Reprogramming" target="_blank">http://wiki.laptop.org/go/Active_Antenna_Reprogramming</a><br>
><br>
> and ensure that the antenna is running v. 3107 of the firmware.<br>
><br>
> A less likely possibility is actual hardware failure. You might<br>
> open the<br>
> Antenna and make sure that the USB connection is still well soldered.<br>
><br>
> John<br>
><br>
> On Feb 15, 2008, at 1:22 AM, sulochan acharya wrote:<br>
><br>
> > Hi all,<br>
> > I am having trouble getting two active antennas connected to the<br>
> > server.<br>
> ><br>
> > This is what happens:<br>
> ><br>
> > 1.When i try to connect two antennas to the server and then start<br>
> it:<br>
> > ERROR:<br>
> ><br>
> > klogctl: Invalid argument<br>
> ><br>
> > Starting udev: Intel_rng: FWH not detected<br>
> ><br>
> > libertas: firmware ini failed<br>
> > And the server would not boot. It would just give libertas: tx<br>
> > watchdog timeout error.<br>
> ><br>
> > I also got the following error:<br>
> ><br>
> > Warning : at /home/dwmw2/olpc-2.6/drivers/net/wireless/libertas/<br>
> > if_usb.c:413 usb_tx_block() (Not tainted)<br>
> > [<f8a06297>] usb_tx_block+0xb0/0xfa [usb8xxx]<br>
> > ...<br>
> > ...<br>
> > ...<br>
> > ...<br>
> > Another error message:<br>
> > Libertas: EXEC_NEXT_CMD: pending data in-flight!<br>
> > Schoolserver kernel : libertas: EXEC_NEXT_CMD: pending data in-<br>
> flight!<br>
> > Rootlibertas: tx watchdog timeout<br>
> ><br>
> ><br>
> ><br>
> > 2. When i start the server with one antenna it works fine. If i add<br>
> > a second one and do #service network restart<br>
> > it would get suck trying to initiate msh1 ....msh0 is active at<br>
> > this point.<br>
> ><br>
> > Also i get this warning all the time libertas: tx watchdog timeout<br>
> ><br>
> > Is this a known problem? Can someone point me towards the direction<br>
> > to getting this fixed.<br>
> > Is this a driver problem?<br>
> ><br>
> > best,<br>
> > Sulochan<br>
> ><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Server-devel mailing list<br>
> > <a href="mailto:Server-devel@lists.laptop.org">Server-devel@lists.laptop.org</a><br>
> > <a href="http://lists.laptop.org/listinfo/server-devel" target="_blank">http://lists.laptop.org/listinfo/server-devel</a><br>
><br>
><br>
<br>
</div></div></blockquote></div><br>