Hi, The patch you sent me will prevent TX timeouts that will trigger gianfar stop(gfar_stop is causing the soft lockup) & start by network watchdog and will solve my first problem.
But, I have this problem again while running some traffic (ping -s 1500 to and from my device) and configuring MTU or set eth interface down. In both cases gfar_stop sometimes cause soft lockup of 2 minutes. Trace in case of MTU set: BR_1: port 1(eth0) entering forwarding state PHY: mdio@ffe24000:01 - Link is Down PHY: mdio@ffe24000:01 - Link is Up - 100/Half PHY: mdio@ffe24000:01 - Link is Down PHY: mdio@ffe24000:01 - Link is Up - 10/Half PHY: mdio@ffe24000:01 - Link is Down BR_1: port 1(eth0) entering disabled state PHY: mdio@ffe24000:01 - Link is Up - 1000/Full BR_1: port 1(eth0) entering forwarding state BUG: soft lockup - CPU#0 stuck for 120s! [wavman:2348] Modules linked in: xt_physdev xt_state xt_tcpudp ebt_mark ebt_mark_m ebt_limit ebtable_nat ebtable_broute ebtable_filter ebtables iptable_mangle iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack umac online_acs(P) dih(P) netlink_support(P) dfs_addon(P) waran(P) ath_dev(P) ath_rate_atheros(P) addons_shared(P) ath_hal(P) adf asf(P) iptable_filter ip_tables x_tables NIP: c00513b8 LR: c00530b4 CTR: c005304c REGS: c6009880 TRAP: 0901 Tainted: P (2.6.31) MSR: 00029000 <EE,ME,CE> CR: 22028228 XER: 00000000 TASK = cd47aa30[2348] 'wavman' THREAD: c6008000 GPR00: 00000080 c6009930 cd47aa30 00000010 ca690a00 c6009b34 c6009ad8 d1880000 GPR08: 11b6598e 00000000 00000000 c0385f14 00000000 NIP [c00513b8] handle_IRQ_event+0x28/0x13c LR [c00530b4] handle_fasteoi_irq+0x68/0xf0 Call Trace: [c6009930] [00000004] 0x4 (unreliable) [c6009950] [c00530b4] handle_fasteoi_irq+0x68/0xf0 [c6009960] [c0004f04] do_IRQ+0x98/0xb4 [c6009980] [c000fe58] ret_from_except+0x0/0x18 [c6009a40] [c0187ae0] stop_gfar+0x20/0x11c [c6009a60] [c0189360] gfar_change_mtu+0x124/0x164 [c6009a80] [c01d5c30] dev_set_mtu+0x70/0xa4 [c6009a90] [c01e112c] do_setlink+0x1dc/0x348 [c6009ad0] [c01e2a9c] rtnl_newlink+0x330/0x460 [c6009bd0] [c01e2288] rtnetlink_rcv_msg+0x228/0x260 [c6009bf0] [c01ee0e8] netlink_rcv_skb+0x110/0x120 [c6009c10] [c01e204c] rtnetlink_rcv+0x28/0x3c [c6009c30] [c01edd78] netlink_unicast+0x2c4/0x334 [c6009c70] [c01ee7ec] netlink_sendmsg+0x1c8/0x280 [c6009cc0] [c01c4c74] sock_sendmsg+0xac/0xe4 [c6009db0] [c01c4e80] sys_sendmsg+0x1d4/0x284 [c6009f00] [c01c58d4] sys_socketcall+0xe0/0x1f8 [c6009f40] [c000f804] ret_from_syscall+0x0/0x3c Instruction dump: 801f0024 4bfffe3c 9421ffe0 7c0802a6 bf61000c 7c9f2378 90010024 7c7e1b78 80040004 70090020 40820008 7c008146 <3d20c02e> 3ba00000 3b69e138 3b800000 Trace in case of set eth down: PHY: mdio@ffe24000:01 - Link is Up - 1000/Full BR_1: port 1(eth0) entering forwarding state BR_1: port 1(eth0) entering disabled state BR_1: port 1(eth0) entering forwarding state PHY: mdio@ffe24000:01 - Link is Up - 100/Full BUG: soft lockup - CPU#0 stuck for 120s! [ip:8428] Modules linked in: xt_physdev xt_state xt_tcpudp ebt_mark ebt_mark_m ebt_limit ebtable_nat ebtable_broute ebtable_filter ebtables iptable_mangle iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack rpldev umac online_acs(P) dih(P) netlink_support(P) dfs_addon(P) waran(P) ath_dev(P) ath_rate_atheros(P) addons_shared(P) ath_hal(P) adf asf(P) iptable_filter ip_tables x_tables NIP: c00513b8 LR: c00530b4 CTR: c005304c REGS: ca663bc0 TRAP: 0901 Tainted: P (2.6.31) MSR: 00029000 <EE,ME,CE> CR: 22020428 XER: 00000000 TASK = c55c7390[8428] 'ip' THREAD: ca662000 GPR00: 00000080 ca663c70 c55c7390 00000010 c627cb00 c0364ae8 00000008 d1880000 GPR08: 4800f86b 00000000 00000000 c0385f14 00000000 NIP [c00513b8] handle_IRQ_event+0x28/0x13c LR [c00530b4] handle_fasteoi_irq+0x68/0xf0 Call Trace: [ca663c70] [ca662000] 0xca662000 (unreliable) [ca663c90] [c00530b4] handle_fasteoi_irq+0x68/0xf0 [ca663ca0] [c0004f04] do_IRQ+0x98/0xb4 [ca663cc0] [c000fe58] ret_from_except+0x0/0x18 [ca663d80] [c0187af8] stop_gfar+0x38/0x11c [ca663da0] [c01882c0] gfar_close+0x30/0xa0 [ca663dc0] [c01d62ec] dev_close+0x8c/0xe0 [ca663dd0] [c01d5db8] dev_change_flags+0x154/0x1ac [ca663df0] [c022277c] devinet_ioctl+0x648/0x824 [ca663e60] [c0223294] inet_ioctl+0xcc/0xf8 [ca663e70] [c01c3c08] sock_ioctl+0x10c/0x2d0 [ca663e90] [c008bc60] vfs_ioctl+0x34/0x8c [ca663ea0] [c008be84] do_vfs_ioctl+0x88/0x724 [ca663f10] [c008c560] sys_ioctl+0x40/0x74 [ca663f40] [c000f804] ret_from_syscall+0x0/0x3c Instruction dump: 801f0024 4bfffe3c 9421ffe0 7c0802a6 bf61000c 7c9f2378 90010024 7c7e1b78 80040004 70090020 40820008 7c008146 <3d20c02e> 3ba00000 3b69e198 3b800000 A script (test_eth) that I run can reproduce it on my board. Did you encounter such problem before ? Thanks in advance, Avi Tsarfati. From: Claudiu Manoil [mailto:claudiu.man...@freescale.com] Sent: Tuesday, October 09, 2012 6:37 PM To: Avi Tsarfati Cc: linuxppc-dev@lists.ozlabs.org Subject: Re: gianfar driver crash on P1020 Hello, Did you try this patch? http://patchwork.ozlabs.org/patch/186315/ Claudiu On 10/9/2012 3:22 PM, Avi Tsarfati wrote: Hi, I have the same problem as you do. Have you found the CPU stuck reason (or fix) in P1020RDB board ? Thanks, Avi Tsarfati. ************************************************************************ ************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses(187). ************************************************************************ ************ _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev ************************************************************************ ************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses(100). ************************************************************************ ************ ************************************************************************ ************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses(42). ************************************************************************ ************ ************************************************************************************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses(187). ************************************************************************************
test_eth
Description: test_eth
_______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
