On Sunday, May 14, 2017 at 4:38:59 PM UTC-5, Mark Copper wrote:
>
> On Thursday, May 11, 2017 at 6:28:42 PM UTC-5, Mark Copper wrote:
>>
>> Could be broken hardware as well.  OTOH BBBW did work out of the box but 
>> networking failed after kernel update while everything else seems OK.
>>
>> Symptoms: Immediately after flashing image, ifconfig and ip show usb 
>> interfaces but not wlan0--same as when booting from SD card. Later network 
>> probe processes hang and do not return (ip, ifconfig, lshw for example, but 
>> not lsusb). Nor can these processes be killed. 
>>
>> Would like to know if anyone else is seeing this.  Would also be glad to 
>> provide additional information.  I also have additional BBBW cards so could 
>> try to duplicate.
>>
>> Hope I'm not too far off base. Thanks for reading.
>>
>
> For the record this appears to have been a hardware problem--I had no 
> trouble flashing a new BBBW with the same SD image. Apologies for the 
> noise. 
>

This is the strangest thing (for a finite state machine). But now the BBBW 
that worked fine Sunday now exhibits the same behavior: on first light 
networking devices are discovered and configured. An undetermined but short 
while later wlan0 does not respond; ifconfig command engenders a process 
that hangs and cannot be killed by kill -9.

So now this has occurred on 2 new BBBW's. The first time it occurred the 
machine was powered through USB so quality of power source seems less 
likely.  Best assumption now seems to be problem with the 4.9.25-ti-r32 
kernel.  So I'll test with older kernel for now.

Would love to know if anyone else has had success with current kernel on 
BBBW. 

Thanks.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ae39d60b-63df-4ce2-8195-5a79a70dcf8a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to