From: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Cc: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>,
"Dave Jones" <davej@suse.de>,
"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 17:42:27 +0100 [thread overview]
Message-ID: <20020325164227.GA19001@merlin.emma.line.org> (raw)
In-Reply-To: <200203250336.08428.Dieter.Nuetzel@hamburg.de> <20020325123942.A23014@suse.de> <200203251540.37393.Dieter.Nuetzel@hamburg.de> <20020325163621.GA21260@woaf.net>
On Mon, 25 Mar 2002, David Flynn wrote:
> 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 ?
Of course, but you cannot tell if you run XPs in SMP configurations. If
you bad things still happen in uniprocessor mode, you know where to
look: at the driver.
--
Matthias Andree
next prev parent reply other threads:[~2002-03-25 16:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-25 2:36 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
2002-03-25 16:42 ` Matthias Andree [this message]
-- 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=20020325164227.GA19001@merlin.emma.line.org \
--to=matthias.andree@stud.uni-dortmund.de \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=davej@suse.de \
--cc=jonathan@woaf.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®