BUG: NETDEV WATCHDOG -> Badness in gianfar driver?

[Andy Fleming]

On Apr 26, 2007, at 12:27, Clemens Koller wrote:

> Hi There!

>
> Any ideas of what could be wrong there? I think there could be a  
> problem
> in the gianfar network driver. Or is there a physical problem with  
> the PHY
> (a Marvell MV88E1111)?

hard to say which.
> Jan  1 03:43:23 ecam kernel: ------------[ cut here ]------------
> Jan  1 03:43:23 ecam kernel: Badness at c003d3d8 [verbose debug  
> info unavailable]
> Jan  1 03:43:23 ecam kernel: Call Trace:
> Jan  1 03:43:23 ecam kernel: [C0355C70] [C0008FE0] show_stack+0x3c/ 
> 0x194 (unreliable)
> Jan  1 03:43:23 ecam kernel: [C0355CA0] [C0135594] report_bug 
> +0xa4/0xac
> Jan  1 03:43:23 ecam kernel: [C0355CB0] [C0003784]  
> program_check_exception+0x2b8/0x460
> Jan  1 03:43:23 ecam kernel: [C0355CD0] [C0002908]  
> ret_from_except_full+0x0/0x4c
> Jan  1 03:43:23 ecam kernel: [C0355D90] [C017B3CC]  
> marvell_ack_interrupt+0x14/0x38
> Jan  1 03:43:23 ecam kernel: [C0355DB0] [C01764A8] stop_gfar+0x54/0xd0
> Jan  1 03:43:23 ecam kernel: [C0355DD0] [C01773D0] gfar_timeout 
> +0x5c/0x68


This is a bit confusing.  Could you identify where in  
marvell_ack_interrupt this is?

Andy