From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755426Ab1BHS2h (ORCPT ); Tue, 8 Feb 2011 13:28:37 -0500 Received: from mail-ew0-f46.google.com ([209.85.215.46]:44066 "EHLO mail-ew0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755401Ab1BHS2f (ORCPT ); Tue, 8 Feb 2011 13:28:35 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=Ux8AOm4RNIubw1ldQUnyLGH0DuE8iezxDJKuYSYfExct3TQ+12inguLwa6Ht8NA7jS isXvfjUkGNQahFWBHw/zf80KQlaRNG+gJFQnw9soWAF+cVf/lQldcpmsiPWpGfm8vu6y ZECUHOKdXFgsvazWCdGYHInyJdSxoK2N/UNi4= Message-ID: <4D518B4D.6020402@googlemail.com> Date: Tue, 08 Feb 2011 19:28:29 +0100 From: "R. Herbst" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20101227 Icedove/3.0.11 MIME-Version: 1.0 To: Benjamin Herrenschmidt CC: linux-kernel@vger.kernel.org, David Miller , Matt , geert@linux-m68k.org Subject: Re: Sun GEM PPC32 Bug? References: <1297056878.14982.65.camel@pasglop> In-Reply-To: <1297056878.14982.65.camel@pasglop> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Here is the cpuinfo: cat /proc/cpuinfo processor : 0 cpu : 7447A, altivec supported clock : 1833.333326MHz revision : 1.1 (pvr 8003 0101) bogomips : 83.31 processor : 1 cpu : 7447A, altivec supported clock : 1833.333326MHz revision : 1.1 (pvr 8003 0101) bogomips : 83.31 total bogomips : 166.63 timebase : 41659035 platform : PowerMac model : PowerMac3,6 machine : PowerMac3,6 motherboard : PowerMac3,6 MacRISC2 MacRISC Power Macintosh detected as : 129 (PowerMac G4 Windtunnel) pmac flags : 00000010 L2 cache : 256K unified pmac-generation : NewWorld Memory : 2048 MB The problems comes only when network going over 40MBit. Have tested with rsync and FTP. Same problem with samba connection. Ragards Rüdiger Herbst On Sun, 2011-02-06 at 16:01 +0100, R. Herbst wrote: > Am 06.02.2011 00:45, schrieb Benjamin Herrenschmidt: > >> >> Actually, the second one is trivial, just modify gem_rxmac_interrupt() >> as follow: >> >> if (rxmac_stat& MAC_RXSTAT_OFLW) { >> u32 smac = readl(gp->regs + MAC_SMACHINE); >> >> netdev_err(dev, "RX MAC fifo overflow smac[%08x]\n", smac); >> gp->net_stats.rx_over_errors++; >> gp->net_stats.rx_fifo_errors++; >> >> - ret = gem_rxmac_reset(gp); >> + ret = 1; >> } >> >> And tell us if that makes a difference. >> >> Cheers, >> Ben. >> >> > Am 07.02.2011 06:34, schrieb Benjamin Herrenschmidt: > What's your machine model (cat /proc/cpuinfo) and what do you do to > trigger the problem ? I'm trying to reproduce here and so far had > no success doing so. > > Cheers, > Ben. > >> Okay. I have made the change. The only difference is that: >> >> In /var/log/messages >> Feb 6 15:52:12 G4 kernel: gem 0002:20:0f.0: eth0: RX MAC fifo >> overflow smac[00810400] >> Feb 6 15:52:12 G4 kernel: gem 0002:20:0f.0: eth0: Link is up at 1000 >> Mbps, full-duplex >> Feb 6 15:52:12 G4 kernel: gem 0002:20:0f.0: eth0: Pause is disabled >> Feb 6 15:57:10 G4 kernel: NETDEV WATCHDOG: eth0 (gem): transmit queue >> 0 timed out >> Feb 6 15:57:10 G4 kernel: ------------[ cut here ]------------ >> Feb 6 15:57:10 G4 kernel: WARNING: at net/sched/sch_generic.c:258 >> Feb 6 15:57:10 G4 kernel: Modules linked in: radeon ttm >> drm_kms_helper drm hwmon power_supply ipv6 snd_pcm_oss snd_mixer_oss >> snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device >> snd_powermac snd_pcm snd_timer snd soundcore snd_page_alloc dm_mod >> uninorth_agp sungem agpgart sungem_phy >> Feb 6 15:57:10 G4 kernel: NIP: c03dceec LR: c03dceec CTR: 00000001 >> Feb 6 15:57:10 G4 kernel: REGS: effefe20 TRAP: 0700 Not tainted >> (2.6.37-gentoo) >> Feb 6 15:57:10 G4 kernel: MSR: 00029032 CR: >> 44200084 XER: 20000000 >> Feb 6 15:57:10 G4 kernel: TASK = ef854cb0[0] 'swapper' THREAD: ef878000 CPU: 1 >> Feb 6 15:57:10 G4 kernel: GPR00: c03dceec effefed0 ef854cb0 0000003e >> 00001032 ffffffff c059f182 2074696d >> Feb 6 15:57:10 G4 kernel: GPR08: 000069f7 effee000 01ea1000 00000004 >> ffffffff fff80b18 fff80154 00000000 >> Feb 6 15:57:10 G4 kernel: GPR16: 00000420 c03dcd4c c0589084 00200200 >> c04c9786 ef888814 ef888a14 ef888c14 >> Feb 6 15:57:10 G4 kernel: GPR24: 00000001 ffffffff ef12e7a0 00000002 >> 00000001 00000000 ef8141d4 ef814000 >> Feb 6 15:57:10 G4 kernel: NIP [c03dceec] dev_watchdog+0x1a0/0x2e4 >> Feb 6 15:57:10 G4 kernel: LR [c03dceec] dev_watchdog+0x1a0/0x2e4 >> Feb 6 15:57:10 G4 kernel: Call Trace: >> Feb 6 15:57:10 G4 kernel: [effefed0] [c03dceec] >> dev_watchdog+0x1a0/0x2e4 (unreliable) >> Feb 6 15:57:10 G4 kernel: [effeff40] [c0043db4] run_timer_softirq+0x1ac/0x260 >> Feb 6 15:57:10 G4 kernel: [effeffa0] [c003d9cc] __do_softirq+0x118/0x1ec >> Feb 6 15:57:10 G4 kernel: [effefff0] [c0011398] call_do_softirq+0x14/0x24 >> Feb 6 15:57:10 G4 kernel: [ef879ea0] [c000687c] do_softirq+0x88/0xb4 >> Feb 6 15:57:10 G4 kernel: [ef879ec0] [c003d178] irq_exit+0x54/0x74 >> Feb 6 15:57:10 G4 kernel: [ef879ed0] [c000ead4] timer_interrupt+0x154/0x190 >> Feb 6 15:57:10 G4 kernel: [ef879ee0] [c0012080] ret_from_except+0x0/0x14 >> Feb 6 15:57:10 G4 kernel: --- Exception: 901 at cpu_idle+0xe0/0x180 >> Feb 6 15:57:10 G4 kernel: LR = cpu_idle+0xd4/0x180 >> Feb 6 15:57:10 G4 kernel: [ef879fa0] [c000a4f8] cpu_idle+0x170/0x180 >> (unreliable) >> Feb 6 15:57:10 G4 kernel: [ef879fc0] [c044952c] start_secondary+0x314/0x350 >> Feb 6 15:57:10 G4 kernel: [ef879ff0] [00003270] 0x3270 >> Feb 6 15:57:10 G4 kernel: Instruction dump: >> Feb 6 15:57:10 G4 kernel: 2f800001 41be003c 38810008 7fe3fb78 >> 38a00040 4bfe77c9 7fa6eb78 7fe4fb78 >> Feb 6 15:57:10 G4 kernel: 7c651b78 3c60c050 3863ed12 48068721 >> <0fe00000> 38000001 3d20c05c 9809d3bc >> Feb 6 15:57:10 G4 kernel: ---[ end trace 876ff0d47c88271d ]--- >> Feb 6 15:57:10 G4 kernel: gem 0002:20:0f.0: eth0: transmit timed out, resetting >> Feb 6 15:57:10 G4 kernel: gem 0002:20:0f.0: eth0: >> TX_STATE[00000001:00000000:00000001] >> Feb 6 15:57:10 G4 kernel: gem 0002:20:0f.0: eth0: >> RX_STATE[0609441d:00000001:00000001] >> Feb 6 15:57:10 G4 kernel: gem 0002:20:0f.0: eth0: Link is up at 1000 >> Mbps, full-duplex >> Feb 6 15:57:10 G4 kernel: gem 0002:20:0f.0: eth0: Pause is disabled >> --- >> It seems that the Network dies and halt for ca. 25 seconds. After a >> while it comes a call trace and the rsync session is dead. But not the >> hole system dies. >> >> Regards >> Rüdi >> > >