From: Patrick Berge <pberge@stny.rr.com>
To: Paul.Mackerras@cs.anu.edu.au
Cc: linuxppc-dev@lists.linuxppc.org,
Justin Vallon <vallon@mindspring.com>,
Keith Jacob <kjacob@chariot.net.au>
Subject: Re: mace:transmit timeout - resetting
Date: Wed, 11 Aug 1999 19:32:00 -0400 [thread overview]
Message-ID: <37B207F0.5F5B197A@stny.rr.com> (raw)
In-Reply-To: 199908100606.QAA23344@tango.anu.edu.au
Paul Mackerras wrote:
> Patrick Berge <pberge@stny.rr.com> wrote:
>
> > I have am receiving "mace:transmit timeout - resetting" sporadically.
>
> But do you see any problems with the network apart from the message?
>
> The reason for the message is that there are some bugs in the mace
> chip which cause it to lock up very occasionally. When the driver
> detects this condition, it prints this message and tries to reset the
> chip. If your network keeps working, then it means that the driver
> successfully got the mace chip going again.
>
> > Any ideas about my problem and/or the meaning of the HZ would be
> > helpful.
>
> HZ is the number of timer interrupts per second.
>
> Paul.
Thanks for the info. For the record I have a PowerPC 7200/120 and was
wondering if any other extended ethernet users have this same problem. The
network works but is incredibly slow do to the resetting every second. I
really don't think the network ever was completely hung... just very very
slow ..like 10,100,1000 times slower than all the other non-mace
machines. I talked to Apple (they just told me the only known problem is
with certain 7200/90 machines (see
http://til.info.apple.com/techinfo.nsf/artnum/n18944) . I guess this is
the issue Keith mentioned in a previous post. I ask them to review there
database and search for any ethernet issues for 7200/120 and they claimed
there are no known ethernet problems.
I guess my question to you, Paul, is what do I need to do to the mace.c
file to turn off the resetting of the chip. I am just guessing that the
reset condition you looked for does not hang the mace chip in the
7200/120. If so then removing the reset should fix my problem. I am
again assuming the the mace chip in my 7200/120 hardware does not hang.
If I remove the resetting and it hangs then well I just have to but a PCI
ethernet card.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
prev parent reply other threads:[~1999-08-11 23:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-10 3:59 mace:transmit timeout - resetting Patrick Berge
1999-08-10 6:06 ` Paul Mackerras
1999-08-10 6:50 ` Patrick Berge
1999-08-11 23:32 ` Patrick Berge [this message]
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=37B207F0.5F5B197A@stny.rr.com \
--to=pberge@stny.rr.com \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=kjacob@chariot.net.au \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=vallon@mindspring.com \
/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).