You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

11:45   Low lost communication with its emerald boards.

rebooted low and everything back up.

Information for Gordon:

root@low root# irqs
Counting interrupts over 5 seconds ...

IRQ      Interrupt Type            Total Int  Int/sec  
------------------------------------------------------
24:      GPIO-l eth0:              2          0.4      
36:      SC serial:                15         3        
37:      SC serial:                102        20.4     
42:      SC ost0:                  508        101.6    
114:     GPIO isp116x-hcd:usb1:    290        58       
115:     GPIO serial:              226        45.2     
116:     GPIO serial:              103        20.6     

end of dmesg

i2c i2c-0: i2c_pxa: timeout waiting for bus free
i2c i2c-0: i2c_pxa: timeout waiting for bus free
i2c i2c-0: i2c_pxa: timeout waiting for bus free
i2c i2c-0: i2c_pxa: timeout waiting for bus free
i2c i2c-0: i2c_pxa: timeout waiting for bus free
i2c i2c-0: i2c_pxa: timeout waiting for bus free
handle_IRQ_event called 4 times for IRQ 3
handle_IRQ_event called 4 times for IRQ 3
root@low root#
root@low root#

Added by Gordon, Jun 26:

/var/log/isfs/kernel has those dmesg messages, with timetags

Jun 23 16:49:50 low kernel: i2c i2c-0: i2c_pxa: timeout waiting for bus free
Jun 23 16:49:53 low last message repeated 5 times
Jun 25 09:27:58 low kernel: handle_IRQ_event called 4 times for IRQ 3
Jun 25 17:46:14 low kernel: handle_IRQ_event called 4 times for IRQ 3

So it turns out those messages are old and aren't much help.

I believe a adn/aup will bring it back too.

I just updated the xml on low so that every sensor has a timeout. That should help to recover from this situation more quickly.

  • No labels