From: Andrew Morton <akpm@zip.com.au>
To: john slee <indigoid@higherplane.net>
Cc: Zwane Mwaikambo <zwane@linux.realnet.co.sz>,
Helge Hafting <helgehaf@aitel.hist.no>,
"Ronny T. Lampert (EED)" <Ronny.Lampert@eed.ericsson.se>,
linux-kernel@vger.kernel.org
Subject: Re: 3c59x driver: card not responding after a while
Date: Mon, 03 Jun 2002 13:12:45 -0700 [thread overview]
Message-ID: <3CFBCDBD.DF675D57@zip.com.au> (raw)
In-Reply-To: <3CFB21C5.27BBFB66@aitel.hist.no> <Pine.LNX.4.44.0206031050170.10836-100000@netfinity.realnet.co.sz> <20020603125752.GE12322@higherplane.net>
john slee wrote:
>
> On Mon, Jun 03, 2002 at 10:51:34AM +0200, Zwane Mwaikambo wrote:
> > On Mon, 3 Jun 2002, Helge Hafting wrote:
> >
> > > I see this too. I always thought it was the less-than-perfect ABIT BP6
> > > loosing an irq or something. (odd that it _always_ is the NIC that goes
> > > though...) I also have a k6 with the same NIC, and another
> > > UP machine at work. They never fail this way.
> > > Could it be a SMP problem?
> >
> > I wouldn't think so, i use it on SMP extensively without a hitch.
>
> "me too" - have been using 3c905B cards in various SMP (and UP) boxes
> for a couple of years now and they've never failed me, even on bp6. in
> fact i seem to have missed out on the plague of bp6 problems, even when
> running dual 300a overclocked to 450. strange.
>
That driver is solid for SMP. It's possible that the BP6
is losing its IRQ routing assignments, or the APIC is
getting stuck. We had extensive problems with that last
year. A workaround was implemented and as far as I can tell,
the problem went away.
It seems to affect network cards most because they typically
generate the most interrupts.
Try booting the machine with the `noapic' option.
-
next prev parent reply other threads:[~2002-06-03 20:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-31 15:34 3c59x driver: card not responding after a while Ronny T. Lampert (EED)
2002-05-31 22:07 ` Scott McDermott
2002-06-01 7:10 ` Zwane Mwaikambo
2002-06-03 7:59 ` Helge Hafting
2002-06-03 8:51 ` Zwane Mwaikambo
2002-06-03 12:57 ` john slee
2002-06-03 20:12 ` Andrew Morton [this message]
2002-06-03 23:35 ` François Cami
2002-06-05 8:11 ` Ronny T. Lampert (EED)
2002-06-03 13:11 ` Joe Korty
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=3CFBCDBD.DF675D57@zip.com.au \
--to=akpm@zip.com.au \
--cc=Ronny.Lampert@eed.ericsson.se \
--cc=helgehaf@aitel.hist.no \
--cc=indigoid@higherplane.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linux.realnet.co.sz \
/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