public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeremy Jackson" <jerj@coplanar.net>
To: "Ben Greear" <greearb@candelatech.com>, "Tim Hockin" <thockin@sun.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	<arjanv@redhat.com>, <saw@sw-soft.com>, <sparker@sparker.net>
Subject: Re: [PATCH] eepro100 - need testers
Date: Fri, 28 Dec 2001 10:52:28 -0800	[thread overview]
Message-ID: <00cd01c18fd0$ced54f20$d90aa8c0@bridge> (raw)
In-Reply-To: <E167w6n-0001dz-00@fenrus.demon.nl> <3C0D54DF.4E897B70@sun.com> <3C269FF1.5040402@candelatech.com>

I have a friend who has had headaches with a D815EEA board with a 2nd
eepro100+ nic installed.
He compiled a new kernel and used a driver from intel's website, and it's
all good now.
FYI
----- Original Message -----
From: "Ben Greear" <greearb@candelatech.com>
To: "Tim Hockin" <thockin@sun.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>;
<arjanv@redhat.com>; <saw@sw-soft.com>; <sparker@sparker.net>
Sent: Sunday, December 23, 2001 7:24 PM
Subject: Re: [PATCH] eepro100 - need testers


> I just tried this patch against the 2.4.17 kernel.  I was able to
> completely freeze my D815EEA2 motherboard based computer by trying
> to copy a large directory over NFS.  The machine is connected to a
> 10bt HUB, and this setup has shown lockups before with various
> eepro100 drivers.  The e100 seems to work fine in this setup...
>
> An older eepro driver (the one with RH's 2.4.9-13 kernel) does not
> lock up the machine, but I do see incessant wait-for-cmd-done-timeout
> messages, and the network is basically un-usable.
>
> On other machines, connected to a 100bt-FD switch, the new patch
> seems to work just fine, btw.
>
> The eepro lockup is repeatable, so let me know if there is any
> information I can get for you that will help.
>
> Thanks,
> Ben
>
> Tim Hockin wrote:
>
> > This patch was developed here to resolve a number of eepro100 issues we
> > were seeing. I'd like to get people to try this on their eepro100 chips
and
> > beat on it for a while.
> >
> > volunteers?
>
>
> --
> Ben Greear <greearb@candelatech.com>       <Ben_Greear AT excite.com>
> President of Candela Technologies Inc      http://www.candelatech.com
> ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>


  reply	other threads:[~2001-12-28 18:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E167w6n-0001dz-00@fenrus.demon.nl>
2001-12-04 22:57 ` [PATCH] eepro100 - need testers Tim Hockin
2001-12-04 23:15   ` Edward Muller
2001-12-05  1:26   ` Kurt Roeckx
2001-12-05 16:59   ` Steve Parker
2001-12-05 19:36     ` Mike Fedyk
2001-12-06 23:34   ` Alan Cox
2001-12-06 23:28     ` Tim Hockin
2001-12-06 23:36     ` Jeff Garzik
2001-12-07  1:05       ` Tim Hockin
2001-12-10  3:42   ` Ben Greear
2001-12-24  3:24   ` Ben Greear
2001-12-28 18:52     ` Jeremy Jackson [this message]
2001-12-31  3:28       ` Ben Greear
2001-12-07  1:30 Leif Sawyer
  -- strict thread matches above, loose matches on Subject: below --
2001-12-11 15:00 Zwane Mwaikambo
2001-12-29 19:01 Peter Hartzler

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='00cd01c18fd0$ced54f20$d90aa8c0@bridge' \
    --to=jerj@coplanar.net \
    --cc=arjanv@redhat.com \
    --cc=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saw@sw-soft.com \
    --cc=sparker@sparker.net \
    --cc=thockin@sun.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