On Thu, 12 Oct 2000, Keith Owens wrote:
> On Thu, 12 Oct 2000 12:56:09 +0100 (BST),
> Tigran Aivazian <tigran@veritas.com> wrote:
> >one correction -- it was "down and up the interface" that did the trick
> >and not deleting the 64M mtrr entry. I.e. the eepro100 problem is better
> >formulated as "when highmem is enabled one or both eepro100 interfaces
> >sometimes do not work from boot but downing/upping the interface usually
> >helps". When highmem is disabled, so far, _both_ eepro100 interfaces
> >_always_ work on boot.
>
> That may only be coincidence. We have intermittent problems with
> eepro100 under 2.4.0-testx, both ix86 and ia64. The symptoms are "card
> reports no resources" messages; down and up the interface and it
> usually works.
Might be related or not, but I've had nothing but problems with eepro100
until it's forced to use 100/FD. Symptoms include: either no network at
all (driver complaining "card reports no resources") or impossibly slow
and erratic network connections (like "ypcat foo" hanging for a second a
few times in between)
- Panu -
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Oct 15 2000 - 21:00:28 EST