Nelson Prado, 
você brilha sempre. Parabens! O seu sucesso faz muito a todos nós. 
Fidencio Maciel 


Em (20:03:17), [email protected] escreveu: 


>SIMPLESMENTE MARAVILHOSO 
> 
>PARABÉNS PARA NELSON PRADO E EQUIPE 
> 
>MUITO OBRIGADO 
>Paulo Corrêa 
> 
>-----Mensagem original----- 
>De: [email protected] [mailto:[EMAIL PROTECTED] 
>nome de Otavio Bernardes 
>Enviada em: quinta-feira, 3 de novembro de 2005 17:05 
>Para: [email protected] 
>Assunto: [bufalos] Fw: EXPOECE 2005 
> 
>Enviado pelo Nelson: 
> 
>----- Original Message ----- 
>From: Laguna 
>To: Otavio Bernardes 
>Sent: Monday, October 31, 2005 10:33 AM 
>Subject: EXPOECE 2005 
> 
>Terminou ontem a EXPOECE 2005. 
>Na exposição agropecuária mais importante do Ceara, conforme programaram os 
>organizadores, o Búfalo foi a principal atração. 
>Mereceu destaque na imprensa com reportagem de 3/4 de pagina num dos 
>principais jornais do Estado. Também a Gazeta Mercantil produziu entrevista 
>a ser veiculada em seu caderno regionNETDEV WATCHDOG: eth0: transmit timed out
eth0: transmit timed out, IRQ conflict ??
Sendincs89x0: Tx buffer not free!
g discover...
NETDEV WATCHDOG: eth0: transmit timed out
eth0: transmit timed out, IRQ conflict ??
eth0: transmit underrun
Sendincs89x0: Tx buffer not free!
g discover...
NETDEV WATCHDOG: eth0: transmit timed out
eth0: transmit timed out, IRQ conflict ??
eth0: transmit underrun
No lease, forking to background.
 
The above did not 'hang' for long (< 10 secs). On logging in to the board the 
'eth0' device was UP but with no IP address. 
 
mx21# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:11:F5:82:D8:CD
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:8

Upon plugging in the cable - the link light immediately came on.....checking 
the interface configuration again....
 
mx21# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:11:F5:82:D8:CD
          inet addr:172.18.128.186  Bcast:172.18.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:804 (804.0 b)  TX bytes:1770 (1.7 Kb)
          Interrupt:8

I will try the same on a DM6446 to see what happens.
 
Regards
 
Phil Q
 
Phil Quiney, Senior Software Engineer
Trinity Convergence
Cambridge Business Park
Cowley Road
Cambridge CB4 0WZ, UK
T: +44(0)1223-435536
F: +44(0)1223-435560
www.trinityconvergence.com <http://www.trinityconvergence.com/> 

 

________________________________

From: Maupin, Chase [mailto:[EMAIL PROTECTED] 
Sent: 12 September 2008 15:59
To: Phil Quiney; davinci-linux-open-source
Subject: RE: DM355 ethernet issue



Phil,

 

If you do not need the ethernet then you can set ip=off on the bootargs.  If 
not then you can enable ethernet after boot I believe by doing 
"/etc/init.d/network restart".  If you want to boot with ethernet enabled but 
no cable you can try removing the ethernet startup scripts to prevent trying to 
start the ethernet at boot.

 

Sincerely,

Chase Maupin

Software Applications

Catalog DSP Products

e-mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 

phone: (281) 274-3285

________________________________

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Phil Quiney
Sent: Friday, September 12, 2008 4:43 AM
To: davinci-linux-open-source
Subject: DM355 ethernet issue

 

Hi All,

 

We have noticed that if a DM355 is started with the ethernet cable unplugged, 
the boot hangs for a considerable time doing the 'ifup'.

 

The interface is configured with the following lines in 
/etc/network/interfaces...

 

auto eth0
iface eth0 inet dhcp

If the cable is plugged in after the board eventually starts, then nothing 
happens, you get no link light on the connector.

 

Does anybody know a way to fix this?

 

One of our customers reported this on a DM6446 so it looks like it is a common 
issue for both boards. I am going to try a DM6446 myself to confirm this.

 

Incidentally, I tried using netlink to see if the linkup/link down events are 
seen by the driver & passed to netlink. If you allow the DM355 to boot with the 
cable plugged in then start the netlink test program then the events are 
generated as the cable is unplugged and plugged in....

 

root@(none):~# ./netlink_test_dm355
Started watching:
eth0: link down
msg_handler: RTM_NEWLINK
netlink_link_state: Link Down
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
msg_handler: RTM_NEWLINK
netlink_link_state: Link Up

This is a lot better than some boards we have tried ;-)

 

If you ping a host on the network & unplug the cable, then the transmission 
stops - we have seen all kinds of errors on the console on other boards when 
this is done. Plugging the cable back in restores operation as you would expect 
(but don't always get).

 

Regards

 

Phil Q

 

Phil Quiney, Senior Software Engineer
Trinity Convergence
Cambridge Business Park

Cowley Road

Cambridge CB4 0WZ, UK
T: +44(0)1223-435536
F: +44(0)1223-435560

www.trinityconvergence.com <http://www.trinityconvergence.com/> 

 

_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Reply via email to