From: David Flynn <dave@woaf.net>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
Cc: Dave Jones <davej@suse.de>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
Matthias Andree <matthias.andree@stud.uni-dortmund.de>,
jonathan@woaf.net
Subject: Re: Possible problems with D-LINK DFE-550TX (stock sundance driver) under 2.4.18
Date: Mon, 25 Mar 2002 16:36:21 +0000 [thread overview]
Message-ID: <20020325163621.GA21260@woaf.net> (raw)
In-Reply-To: <200203250336.08428.Dieter.Nuetzel@hamburg.de> <20020325123942.A23014@suse.de> <200203251540.37393.Dieter.Nuetzel@hamburg.de>
* Dieter N?tzel (Dieter.Nuetzel@hamburg.de) wrote:
> On Montag, 25. März 2002 :39, Dave Jones wrote:
> > On Mon, Mar 25, 2002 at 03:36:07AM +0100, Dieter Nützel wrote:
> > > > Try booting with just one processor (maxcpus=1 boot option) or borrow
> > > > two Athlon MP and see if you can reproduce the problem then. If you
> > > > can, someone may help you. I you can't reproduce it with one CPU,
> > > > you're probably on your own.
> > >
> > > On "newer" Athlon XP (Duron, Athlon Thoroughbred) L5-4 bridge have to be
> > > closed.
> >
> > You don't for a minute think that there might be a reason that bridge
> > got broken at the factory ? *sigh*, we've been through this topic
> > before, I'm tired of arguing it.
>
> Sure, but some wise men said, "there is nothing that simple on this planet".
> Some Athlon XP/MP are "broken", so they were labeled as XPs.
> In the other case it's simple marketing and business (earning more money).
> You can only argue about the distribution. But your are right, I won't do
> that. I only want to be sure that David didn't have one of the old XPs.
>
> -Dieter
>
Please, do we have to go on about the merits of Athlon XP systems in MP
configurations ?? 1) your wrong about the bridges, it only affects iirc
the new XP2000+ chips, 2) is it /REALLY/ the issue ?? i do not think so.
However, I am very happy to report that the system has just done it
again. I can't give any further details yet, although i am just going
over to pay a visit to the box and do some more investigations.
FYI, we have two of these boxes with the same hardware / kernel
configuration. Two of them have now shown the same problem (eth0
timeouts). Including having maxcpus=1 set.
Could this perhaps be a driver issue after all ?
Many Thanks
Dave
next prev parent reply other threads:[~2002-03-25 16:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-25 2:36 Possible problems with D-LINK DFE-550TX (stock sundance driver) under 2.4.18 Dieter Nützel
2002-03-25 11:39 ` Dave Jones
2002-03-25 14:40 ` Dieter Nützel
2002-03-25 16:36 ` David Flynn [this message]
2002-03-25 16:42 ` Matthias Andree
-- strict thread matches above, loose matches on Subject: below --
2002-03-25 0:48 David Flynn
2002-03-25 2:08 ` Matthias Andree
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=20020325163621.GA21260@woaf.net \
--to=dave@woaf.net \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=davej@suse.de \
--cc=jonathan@woaf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@stud.uni-dortmund.de \
/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