2009-09-17 08:30:08     dm9000 transmit timed out

2009-09-17 08:30:08     dm9000 transmit timed out

roy xue (CHINA)

Message: 80079   

Hi,all

I am using uClinux2009r1-rc6, and bf532 cpu board. but it   dump debug message:

------------[ cut here ]------------

WARNING: at net/sched/sch_generic.c:226 _dev_watchdog+0x1ec/0x1f4()

NETDEV WATCHDOG: eth0 (dm9000): transmit timed out

Modules linked in: wcfxs zaptel bfsi

Hardware Trace:

   0 Target : <0x00004ad0> { _dump_stack + 0x0 }

     Source : <0x0000e160> { _warn_slowpath + 0x58 } CALL pcrel

   1 Target : <0x0000e160> { _warn_slowpath + 0x58 }

     Source : <0x00026c2e> { _print_modules + 0x7a } RTS

   2 Target : <0x00026c28> { _print_modules + 0x74 }

     Source : <0x0000e6e2> { _printk + 0x16 } RTS

   3 Target : <0x0000e6de> { _printk + 0x12 }

     Source : <0x0000ef54> { _vprintk + 0x130 } RTS

   4 Target : <0x0000ef34> { _vprintk + 0x110 }

     Source : <0x0000f078> { _vprintk + 0x254 } JUMP.S

   5 Target : <0x0000f078> { _vprintk + 0x254 }

     Source : <0x0000e556> { _wake_up_klogd + 0x1a } RTS

   6 Target : <0x0000e556> { _wake_up_klogd + 0x1a }

     Source : <0x0000e548> { _wake_up_klogd + 0xc } IF !CC JUMP

   7 Target : <0x0000e53c> { _wake_up_klogd + 0x0 }

     Source : <0x0000e966> { _release_console_sem + 0x1aa } JUMP.L

   8 Target : <0x0000e95e> { _release_console_sem + 0x1a2 }

     Source : <0x0000e952> { _release_console_sem + 0x196 } IF !CC JUMP

   9 Target : <0x0000e950> { _release_console_sem + 0x194 }

     Source : <0x0000e942> { _release_console_sem + 0x186 } IF !CC JUMP

  10 Target : <0x0000e93c> { _release_console_sem + 0x180 }

     Source : <0x00021350> { _up + 0x3c } RTS

  11 Target : <0x0002134a> { _up + 0x36 }

     Source : <0x0002133c> { _up + 0x28 } IF !CC JUMP

  12 Target : <0x00021314> { _up + 0x0 }

     Source : <0x0000e938> { _release_console_sem + 0x17c } CALL pcrel

  13 Target : <0x0000e924> { _release_console_sem + 0x168 }

     Source : <0x0000e80a> { _release_console_sem + 0x4e } IF !CC JUMP

  14 Target : <0x0000e7e2> { _release_console_sem + 0x26 }

     Source : <0x0000e906> { _release_console_sem + 0x14a } IF !CC JUMP

  15 Target : <0x0000e900> { _release_console_sem + 0x144 }

     Source : <0x0000e4aa> { __call_console_drivers + 0x7e } RTS

Stack info:

SP: [0x00195cbc] <0x00195cbc> /* kernel dynamic memory */

FP: (0x00195eb4)

Memory from 0x00195cb0 to 00196000

00195cb0: 00000000  00195cbc  001848a4 [0000e160]<0000e164> 00195cdc  001613a8 <00009a98>

00195cd0: 001613a8  000000e2  00195cdc  7665645f  7461775f  6f646863  78302b67  2f636531

00195cf0: 66317830  00000034  0000001f  00195d24 <00009c16> 0252a234  0252a240  00000000

00195d10: 00000001  00000000  0017a448  00000001  00000000  00195d5c <00009c4c> 0252a258

00195d30: 02529bac  00009c38  0000001f  0000001f  0000000f  e5ad80e2  00000003  00020e32

00195d50:<00015b34> 00000000  00000000  00195d90 <02081caa> 00000000  00000000  0014ff97

00195d70: 00195d8c  00000000  00000000  00000008 <0000a6c6> 0000000a  02529e94  0252a248

00195d90: 1afcf004  f1c4feac  f4c418fc  0e3ce104  02081758 <02088a12> 0000195c <000d3d84>

00195db0: ffffffff  00000100  00187c98  00195de0 <000e0aa0> 00188edc  ffffffff  00000100

00195dd0: 00187c98  0000001f  0209ffc8  e602e653  025a0000  00195de8  30396d64 <00003030>

00195df0:<025919a0> 0252a420  00180660  02528000  e602f1dd  00000000  00000000  00000000

00195e10: 00000000  00195e34 <00015f34> 00000000  00195e54 <00015b34><00015bd0> 0017f29c

00195e30: 00195e4c  000e08b4  00194000  00187c98 <ffa08408> 00180640  00000006  00195e4c

00195e50: 00195e4c  00000001 <000125aa> 0017f18c  00194000  0017f128  00000001  00000004

00195e70: 00000100 <0002b4fc> 00189cd8  00000006  001758a4  00000006  00187c98 <ffa082e6>

00195e90: 001837a4  00194000  001758a4  00000006  00000000  00000000  00000000  00453af4

00195eb0: 0009d842 (00000000)<ffa08b8c> ffc00014  00175004  00000000  00000000  00000000

00195ed0: 00000000  ffa0826c  00008050  00000000  00000000  02202000  0240d8ac  ffa0826c

00195ef0:<ffa08140> 00000006  02002060  00453af5  0009d842  00453af4  0009d842  00000000

00195f10: 00000000  00000916  00000000  003d08d9  00000000  00000000  00000000  00000000

00195f30: 00000000  00000000  00000000  00000000  00000000  00000000  00000000  00000000

00195f50: 00000003  00000000  00000010  00000000  0000c350  00196000  00187c98  ffa0824c

00195f70: 00194000  001758a4  00187c98  00194000  ffa08914  00175004  00000000  00000000

00195f90: 00000000  00000005  00000000  025df380  0000ffff  0000ffff  ffa08914  00000006

00195fb0: 00175004  00000000  00000000  001966d6  00181aec  001ac004  00175010  00175004

00195fd0: 00000000  001ac004  00174bc8  00000017  001960a8  001aea54  00196000  001a1744

00195ff0: 00000000  00000000  00000000  ff900000

Return addresses in stack:

    address : <0x0000e160> { _warn_slowpath + 0x58 }

    address : <0x0000e164> { _warn_slowpath + 0x5c }

    address : <0x00009a98> { _activate_task + 0x34 }

    address : <0x00009c16> { ___wake_up_common + 0x3a }

    address : <0x00009c4c> { ___wake_up + 0x14 }

    address : <0x00015b34> { _run_timer_softirq + 0x14 }

    address : <0x02081caa> { :zaptel:_zt_hdlc_finish + 0x656 }

    address : <0x0000a6c6> { _place_entity + 0xbe }

    address : <0x02088a12> { :zaptel:_zt_receive + 0x12a }

    address : <0x000d3d84> { _netdev_drivername + 0x34 }

    address : <0x000e0aa0> { _dev_watchdog + 0x1ec }

    address : <0x00003030> { _do_signal + 0x450 }

    address : <0x025919a0> { :wcfxs:_regular_interrupt_processing + 0x1d4 }

    address : <0x00015f34> { _run_local_timers + 0x8 }

    address : <0x00015b34> { _run_timer_softirq + 0x14 }

    address : <0x00015bd0> { _run_timer_softirq + 0xb0 }

    address : <0xffa08408> { _timer_interrupt + 0xd4 }

    address : <0x000125aa> { ___do_softirq + 0x5e }

    address : <0x0002b4fc> { _handle_simple_irq + 0x78 }

    address : <0xffa082e6> { _asm_do_IRQ + 0x66 }

   frame  1 : <0xffa08b8c> { __common_int_entry + 0x70 }

    address : <0xffa08140> { _cpu_idle + 0x20 }

---[ end trace c037b77d5737eb5f ]---

I have no idear to this problem. Any advance will be appreciate.

Regards,

Roy

QuoteReplyEditDelete

2009-09-17 10:29:42     Re: dm9000 transmit timed out

Mike Frysinger (UNITED STATES)

Message: 80082   

does the hardware work under u-boot ?  has it ever worked under Linux ?  is it detected properly during boot ?

check your async bank timings.

QuoteReplyEditDelete

2009-09-17 23:18:20     Re: dm9000 transmit timed out

roy xue (CHINA)

Message: 80101   

Hi,Mike

the dm9000 run well on uboot, and it can work under linux, it detected properly during boot too.

the dump appear when load the zaptel driver, after the dump, both the dm9000 and zaptel work fine.

Did you mean to check the hardware pin AMSx waveform?

Roy

QuoteReplyEditDelete

2009-09-22 02:19:35     Re: dm9000 transmit timed out

roy xue (CHINA)

Message: 80214   

I slow down the EBIU and the dump disappear.

Roy

QuoteReplyEditDelete

2009-09-29 04:28:09     Re: dm9000 transmit timed out

roy xue (CHINA)

Message: 80630   

Hi,

I have test many times, the dump doesnot disappear. I doubt the crash the was appear when runing to  ":zaptel:_zt_receive + 0x12a". I check src, around the ":zaptel:_zt_receive + 0x12a", there is a spin_lock_irqsave function. I think the spin lock function lock the kernel  over the _dev_watchdog time, so dump. Am I analyse right? Is it propersbal to set the watchdog time longer? and how.

Regards,

Roy