public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "R. Herbst" <ruediger.herbst@googlemail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org, David Miller <davem@davemloft.net>,
	Matt <jackdachef@gmail.com>,
	geert@linux-m68k.org
Subject: Re: Sun GEM PPC32 Bug?
Date: Tue, 08 Feb 2011 19:28:29 +0100	[thread overview]
Message-ID: <4D518B4D.6020402@googlemail.com> (raw)
In-Reply-To: <1297056878.14982.65.camel@pasglop>

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<EE,ME,CE,IR,DR>   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
>>      
>
>    


  reply	other threads:[~2011-02-08 18:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-06 15:01 Sun GEM PPC32 Bug? R. Herbst
2011-02-07  5:34 ` Benjamin Herrenschmidt
2011-02-08 18:28   ` R. Herbst [this message]
2011-02-08 19:58   ` Andreas Schwab
2011-02-09  0:18     ` Benjamin Herrenschmidt
2011-02-09 17:37       ` Andreas Schwab
  -- strict thread matches above, loose matches on Subject: below --
2011-02-04 16:55 Matt
2011-02-04 20:51 ` Benjamin Herrenschmidt
2011-02-04 22:55   ` David Miller
2011-02-05 18:35     ` R. Herbst
2011-02-05 23:39       ` Benjamin Herrenschmidt
2011-02-05 23:45         ` Benjamin Herrenschmidt
2011-02-06  0:20         ` Matt
2011-02-05 20:32     ` Matt
2011-02-05 23:20       ` Benjamin Herrenschmidt
2011-02-06 14:22       ` R. Herbst
2011-02-03 19:47 R. Herbst
2011-02-04  8:02 ` Geert Uytterhoeven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D518B4D.6020402@googlemail.com \
    --to=ruediger.herbst@googlemail.com \
    --cc=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=geert@linux-m68k.org \
    --cc=jackdachef@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox