From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: <christopher.murtagh@wcg.mcgill.ca>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: mmu_context_overflow
Date: Thu, 15 Feb 2001 23:27:35 +0100 [thread overview]
Message-ID: <19350110155919.4689@smtp.wanadoo.fr> (raw)
In-Reply-To: <Pine.LNX.4.21.0102151523330.3305-100000@saraswati.wcg.mcgill.ca>
> I just saw this message for the first time on one of my machines (G4/450)
>as well. I've been getting a lot of 'eth0: transmit timed out, resetting'
>which would freeze the network in kernel 2.2.17 (I'm now running 2.2.18,
>which seems to survive it). My machine is taking on about 120,000 http
>requests per hour though and there doesn't seem to be any effect on the
>performance. Is this something I should worry about?
>
> Any info would be much appreciated.
No, I don't think you should worry about these. those messages simply
need that the kernel ran out of VSIDs and had to re-assign them all. It's
perfectly harmless as long as it doesn't happen too often.
I'm more concerned about your network problems however. I beleive the
chip is a GMAC chip with a 5201 PHY (can you confirm ?). With 2.2.18, you
should not have transmit timeouts. If you have some, then there's either
a bug in the driver (which seemed to be rock-solid so far) or, we are
hitting a HW issue.
Does the gmac driver display some version informations when the kernel boots ?
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-15 22:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 17:21 mmu_context_overflow Geert Uytterhoeven
2001-02-15 17:29 ` mmu_context_overflow Dan Malek
2001-02-15 20:34 ` mmu_context_overflow christopher.murtagh
2001-02-15 22:27 ` Benjamin Herrenschmidt [this message]
2001-02-16 5:40 ` mmu_context_overflow christopher.murtagh
2001-02-16 8:28 ` mmu_context_overflow Benjamin Herrenschmidt
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=19350110155919.4689@smtp.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=christopher.murtagh@wcg.mcgill.ca \
--cc=linuxppc-dev@lists.linuxppc.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).