From: Eberhard Stoll <eberhard.stoll@berghof.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: MPC5200 ethernet communication stops unexpected
Date: Mon, 21 May 2007 09:43:58 +0200 [thread overview]
Message-ID: <46514DBE.30708@berghof.com> (raw)
In-Reply-To: <5b525e390705150803l516a5d9x9c214e2b4b00ea0e@mail.gmail.com>
Hi,
> xlb = (struct mpc52xx_xlb *)MPC5xxx_XLB;
> out_be32(&xlb->config, in_be32(&xlb->config) | MPC52xx_XLB_CFG_BSDIS);
>
this modification seems to solve my problem, too (ethernet communication
stops unexpected / best comm tx task deadlock(?))!
As i described before ping -f triggered the problem in between 20
minutes everytime. With this patch my configuration to trigger the fault
run from Friday to Monday (> 60h) without any error!
So it seems for me this solved my problem, too!
Best regards,
Eberhard
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
next prev parent reply other threads:[~2007-05-21 7:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1179234357.1668.10.camel@pc-hans>
2007-05-15 15:03 ` MPC5200 ethernet communication stops unexpected David Kanceruk
2007-05-16 6:56 ` Sylvain Munaut
2007-05-21 7:43 ` Eberhard Stoll [this message]
2007-05-16 7:29 Hans Thielemans
2007-05-16 15:25 ` John Rigby
-- strict thread matches above, loose matches on Subject: below --
2007-05-15 15:16 Hans Thielemans
2007-05-15 15:40 ` David Kanceruk
2007-04-20 19:21 Eberhard Stoll
2007-04-27 14:35 ` tacitus
2007-04-27 15:42 ` Daniel Schnell
2007-04-27 17:09 ` Eberhard Stoll
2007-04-27 17:22 ` David Kanceruk
[not found] ` <4632369E.8010000@berghof.com>
2007-04-27 18:15 ` David Kanceruk
2007-04-30 20:49 ` Wolfgang Denk
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=46514DBE.30708@berghof.com \
--to=eberhard.stoll@berghof.com \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).