Honored Contributor
Honored ContributorI have found it!
Even though the description for interrupt "0" says that it can be used for the system timer it is not. As a general rule you should never use interrupt "0" for anything. I did this and the problem was resolved immediately. Carlos --- Quote Start --- originally posted by carlos@Oct 2 2006, 03:42 PM hello gentlemen,
for some reason i have been getting this message
# dhcpcd -nry &
28# eth0:phy 100baset
eth0:phy half duplex
netdev watchdog: eth0: transmit timed out
eth0: transmit timed out, irq conflict?
scheduling while atomic: swapper/0x00000100/0
stack from 021e7dc0:<0>
<0> 00000100<0> 02189158<0> 80020308<0> 021e7e0c<0> 00000000<0> 00000000<
0> 00000000<0> 00000000<0>
<0> 8002030a<0> 80020300<0> 00000000<0> 0226c220<0> 0226c000<0> ffffffff<
0> 00000000<0> 021b6868<0>
<0> ffff97c6<0> 00000033<0> 0218a080<0> 021ffd58<0> 021ffd58<0> ffff97c6<
0> 4b87ad6e<0> 02013088<0>
<0> 021b57b8<0> 021ff720<0> 00007809<0> ffffe000<0> 8002030a<0> 020e6e98<
0> 00000013<0> 020e713c<0>
<0> 00000000<0> 021b6868<0> 021e7e84<0> 021ff720<0> 021e7e84<0> 02134830<
0> 0226c000<0> 0226c000<0>
<0> 021e7f3c<0> 020e72f8<0> 021b6868<0> 0226c000<0> 021348d0<0> 00000100<
0> ffffe000<0> 020127b8<0>
call trace:<0>
<0> <0> <0> <0> <0>
<0> <0> <0> <0> <0>
<0> <0> <0> <0> <0>
<0> <0>
bad: scheduling from the idle thread!
stack from 021e7dc0:<0>
<0> ffffffff<0> 0218906c<0> 80020308<0> 021e7e0c<0> 00000000<0> 00000000<
0> 00000000<0> 00000000<0>
<0> 8002030a<0> 80020300<0> 00000000<0> 0226c220<0> 0226c000<0> ffffffff<
0> 00000000<0> 021b6868<0>
<0> ffff97c6<0> 00000033<0> 0218a080<0> 021ffd58<0> 021ffd58<0> ffff97c6<
0> 4b87ad6e<0> 02013088<0>
<0> 021b57b8<0> 021ff720<0> 00007809<0> ffffe000<0> 8002030a<0> 020e6e98<
0> 00000013<0> 020e713c<0>
<0> 00000000<0> 021b6868<0> 021e7e84<0> 021ff720<0> 021e7e84<0> 02134830<
0> 0226c000<0> 0226c000<0>
<0> 021e7f3c<0> 020e72f8<0> 021b6868<0> 0226c000<0> 021348d0<0> 00000100<
0> ffffe000<0> 020127b8<0>
call trace:<0>
<0> <0> <0> <0> <0>
<0> <0> <0> <0> <0>
<0> <0> <0> <0> <0>
<0> <0>
i have tried recompiling the kernel from scratch, no avail, redoing the file system, same thing.
i reduced to the very basic components and see the same results.
i have configured /etc/rc to do nothing with ehternet on power up init.
after the board comes up, i connect (nios2-terminal) see all the messages go by, and as soon as i enter "dhcpcd -nry&" at the console, i get these messages.
please lend a hand to a fellow engineer,
thanks,
carlos
<div align='right'><{post_snapback}> (index.php?act=findpost&pid=18520)</div> --- Quote End ---
