From tomscarlet@hotmail.com Tue Jul 9 02:53:01 2002
From: tomscarlet@hotmail.com (Tom Scarlet)
Date: Tue Jul 9 01:53:01 2002
Subject: [realtek-bug] Ancient bread recipe actually helps you lose weight!
Message-ID: <200207090552.g695qRO01046@blueraja.scyld.com>
Hunza Bread
Hunza Bread
Home made Hunza Bread is a simple, delicious and
nutritious bread that is easily prepared in just 5 minutes
using a few ingredients that have
always been universally available. The taste of this bread is
wonderful.
HUNZA BREAD Miraculously Stops Your Appetite And
Hunger and is based on a 2000 year old recipe
The Hunzas are considered to be the healthiest people
on earth. This bread is the main part of their diet.
CLICK HERE to learn more about these astounding people and
their delicious,
nutritious and easy to prepare home made health bread that
suppresses your appetite.
From dmiller@Kromos.COM Wed Jul 24 18:01:04 2002
From: dmiller@Kromos.COM (Dan Miller)
Date: Wed Jul 24 17:01:04 2002
Subject: [realtek-bug] problem: rtl8139 V1.17 and Linux kernel 2.2.19
Message-ID: <003101c23355$273bc360$c40112ac@kromos.com>
We're trying to use a Realtek Ethernet chip (built into the motherboard) on a Linux 2.2.19 system.
We originally using rtl8139.c version 1.07, but after a few hours under heavy loads (WebStone with 500 connections) it would start to report errors of various sorts. Today, we tried upgrading to version 1.17, from the scyld web site. We also obtained pci-scan.c and the required headers from this same page. When we load this driver pair, it loads successfully, but when we try to ping through the driver, in reports:
eth0: Abnormal interrupt, status 00000020.
eth0: Abnormal interrupt, status 00002020.
Has anyone ever seen this?? Any idea why this would happen?? We rebooted the system, and it's not happening now...
---
soooo... if Nasdaq drops below $1, will it delist itself??
From becker@scyld.com Wed Jul 24 18:36:00 2002
From: becker@scyld.com (Donald Becker)
Date: Wed Jul 24 17:36:00 2002
Subject: [realtek-bug] problem: rtl8139 V1.17 and Linux kernel 2.2.19
In-Reply-To: <003101c23355$273bc360$c40112ac@kromos.com>
Message-ID:
On Wed, 24 Jul 2002, Dan Miller wrote:
> We're trying to use a Realtek Ethernet chip (built into the
> motherboard) on a Linux 2.2.19 system.
>
> We originally using rtl8139.c version 1.07, but after a few hours
> under heavy loads (WebStone with 500 connections) it would start to
> report errors of various sorts. Today, we tried upgrading to version
> 1.17, from the scyld web site. We also obtained pci-scan.c and the
> required headers from this same page. When we load this driver pair,
> it loads successfully, but when we try to ping through the driver, in
> reports:
>
> eth0: Abnormal interrupt, status 00000020.
> eth0: Abnormal interrupt, status 00002020.
Hmmm, this could be either a link change indication (overloaded on the
RxUnderrun indication), or a RxUnderrun. Which chip do you have, and
what is the detection message? If it's a rtl8139c, the second status
indicates that the cable has changed length -- perhaps due to the link
returning.
--
Donald Becker becker@scyld.com
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210 Second Generation Beowulf Clusters
Annapolis MD 21403 410-990-9993
From dmiller@Kromos.COM Wed Jul 24 18:45:00 2002
From: dmiller@Kromos.COM (Dan Miller)
Date: Wed Jul 24 17:45:00 2002
Subject: [realtek-bug] problem: rtl8139 V1.17 and Linux kernel 2.2.19
In-Reply-To:
Message-ID: <003701c2335b$43273a40$c40112ac@kromos.com>
Oh, that was it!! My co-worker had switched cables to try to solve a perceived comm problem, and we get the first message when we disconnect, and the second when we re-connect!! We just confirmed it by connecting and disconnecting the cable again... Great...
Thanks for your quick help!!
> -----Original Message-----
> From: Donald Becker [mailto:becker@scyld.com]
> Sent: Wednesday, July 24, 2002 14:36
> To: Dan Miller
> Cc: realtek-bug@scyld.com
> Subject: Re: [realtek-bug] problem: rtl8139 V1.17 and Linux kernel
> 2.2.19
>
>
> On Wed, 24 Jul 2002, Dan Miller wrote:
>
> > We're trying to use a Realtek Ethernet chip (built into the
> > motherboard) on a Linux 2.2.19 system.
> >
> > We originally using rtl8139.c version 1.07, but after a few hours
> > under heavy loads (WebStone with 500 connections) it would start to
> > report errors of various sorts. Today, we tried upgrading
> to version
> > 1.17, from the scyld web site. We also obtained pci-scan.c and the
> > required headers from this same page. When we load this
> driver pair,
> > it loads successfully, but when we try to ping through the
> driver, in
> > reports:
> >
> > eth0: Abnormal interrupt, status 00000020.
> > eth0: Abnormal interrupt, status 00002020.
>
> Hmmm, this could be either a link change indication (overloaded on the
> RxUnderrun indication), or a RxUnderrun. Which chip do you have, and
> what is the detection message? If it's a rtl8139c, the second status
> indicates that the cable has changed length -- perhaps due to the link
> returning.
>
> --
> Donald Becker becker@scyld.com
> Scyld Computing Corporation http://www.scyld.com
> 410 Severn Ave. Suite 210 Second Generation
> Beowulf Clusters
> Annapolis MD 21403 410-990-9993
>
From becker@scyld.com Wed Jul 24 21:26:01 2002
From: becker@scyld.com (Donald Becker)
Date: Wed Jul 24 20:26:01 2002
Subject: [realtek-bug] problem: rtl8139 V1.17 and Linux kernel 2.2.19
In-Reply-To: <003701c2335b$43273a40$c40112ac@kromos.com>
Message-ID:
On Wed, 24 Jul 2002, Dan Miller wrote:
> Oh, that was it!! My co-worker had switched cables to try to solve a
> perceived comm problem, and we get the first message when we
> disconnect, and the second when we re-connect!! We just confirmed it
> by connecting and disconnecting the cable again... Great...
OK, this extra message is noted as a buglet. The message level is
NETIF_MSG_DRV, when it is closer to NETIF_MSG_LINK.
--
Donald Becker becker@scyld.com
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210 Second Generation Beowulf Clusters
Annapolis MD 21403 410-990-9993
From dmiller@Kromos.COM Thu Jul 25 13:48:38 2002
From: dmiller@Kromos.COM (Dan Miller)
Date: Thu Jul 25 12:48:38 2002
Subject: [realtek-bug] rtl8139 - another repeating error (??)
Message-ID: <004201c233fa$0053d5d0$c40112ac@kromos.com>
We're still running our test system as defined previously: WebStone with 500 connections... We find that periodically through the night (about once every 1-3 minutes) we get the following message on the receive side:
eth0: Transmit timeout, status 0d 0000 media 10.
Is this a sign of something actually failing??? Or is it just a "I'm really busy" type of message??
soooo... if Nasdaq drops below $1, will it delist itself??
From becker@scyld.com Thu Jul 25 15:38:01 2002
From: becker@scyld.com (Donald Becker)
Date: Thu Jul 25 14:38:01 2002
Subject: [realtek-bug] rtl8139 - another repeating error (??)
In-Reply-To: <004201c233fa$0053d5d0$c40112ac@kromos.com>
Message-ID:
On Thu, 25 Jul 2002, Dan Miller wrote:
> We're still running our test system as defined previously: WebStone
> with 500 connections... We find that periodically through the night
> (about once every 1-3 minutes) we get the following message on the
> receive side:
>
> eth0: Transmit timeout, status 0d 0000 media 10.
The older driver versions, from over a year ago, had a false-trigger
window for this message on SMP machines. The interrupt handler could be
delayed long enough for another processor to think that the interrupt
had not been handled.
What version are you using?
--
Donald Becker becker@scyld.com
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210 Second Generation Beowulf Clusters
Annapolis MD 21403 410-990-9993
From dmiller@Kromos.COM Thu Jul 25 15:45:01 2002
From: dmiller@Kromos.COM (Dan Miller)
Date: Thu Jul 25 14:45:01 2002
Subject: [realtek-bug] rtl8139 - another repeating error (??)
In-Reply-To:
Message-ID: <004701c2340b$46f65ab0$c40112ac@kromos.com>
We're using version 1.17, from the Scyld website.
We're not in a multiprocessor environment; should this message be controlled by an "#ifdef __SMP" or some such control??
> -----Original Message-----
> From: Donald Becker [mailto:becker@scyld.com]
> Sent: Thursday, July 25, 2002 11:38
> To: Dan Miller
> Cc: realtek-bug@scyld.com; David Peavey (Work) (E-mail)
> Subject: Re: [realtek-bug] rtl8139 - another repeating error (??)
>
>
> On Thu, 25 Jul 2002, Dan Miller wrote:
>
> > We're still running our test system as defined previously: WebStone
> > with 500 connections... We find that periodically through the night
> > (about once every 1-3 minutes) we get the following message on the
> > receive side:
> >
> > eth0: Transmit timeout, status 0d 0000 media 10.
>
> The older driver versions, from over a year ago, had a false-trigger
> window for this message on SMP machines. The interrupt
> handler could be
> delayed long enough for another processor to think that the interrupt
> had not been handled.
>
> What version are you using?
>
> --
> Donald Becker becker@scyld.com
> Scyld Computing Corporation http://www.scyld.com
> 410 Severn Ave. Suite 210 Second Generation
> Beowulf Clusters
> Annapolis MD 21403 410-990-9993
>
From becker@scyld.com Thu Jul 25 17:09:00 2002
From: becker@scyld.com (Donald Becker)
Date: Thu Jul 25 16:09:00 2002
Subject: [realtek-bug] rtl8139 - another repeating error (??)
In-Reply-To: <004701c2340b$46f65ab0$c40112ac@kromos.com>
Message-ID:
On Thu, 25 Jul 2002, Dan Miller wrote:
> We're using version 1.17, from the Scyld website.
> We're not in a multiprocessor environment; should this message be controlled by an "#ifdef __SMP" or some such control??
That version should not have the false-trigger window.
What is the link partner? Is it possible that this is the link beat
dropping?
--
Donald Becker becker@scyld.com
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210 Second Generation Beowulf Clusters
Annapolis MD 21403 410-990-9993
From dmiller@Kromos.COM Thu Jul 25 17:27:01 2002
From: dmiller@Kromos.COM (Dan Miller)
Date: Thu Jul 25 16:27:01 2002
Subject: [realtek-bug] rtl8139 - another repeating error (??)
In-Reply-To:
Message-ID: <004801c23419$96c82100$c40112ac@kromos.com>
The source code *does* still have the message, in
static void rtl8129_tx_timeout(struct net_device *dev);
The link partner is a Netgear FS108 Switch. I don't know whether the link beat is dropping, though webstone *does* put a heavy load on the system (both in amount of traffic and in number of TCP connections) ...
> -----Original Message-----
> From: Donald Becker [mailto:becker@scyld.com]
> Sent: Thursday, July 25, 2002 13:09
> To: Dan Miller
> Cc: realtek-bug@scyld.com; 'David Peavey (Work) (E-mail)'
> Subject: RE: [realtek-bug] rtl8139 - another repeating error (??)
>
>
> On Thu, 25 Jul 2002, Dan Miller wrote:
>
> > We're using version 1.17, from the Scyld website.
> > We're not in a multiprocessor environment; should this
> message be controlled by an "#ifdef __SMP" or some such control??
>
> That version should not have the false-trigger window.
>
> What is the link partner? Is it possible that this is the link beat
> dropping?
>
> --
> Donald Becker becker@scyld.com
> Scyld Computing Corporation http://www.scyld.com
> 410 Severn Ave. Suite 210 Second Generation
> Beowulf Clusters
> Annapolis MD 21403 410-990-9993
>
From becker@scyld.com Thu Jul 25 18:17:01 2002
From: becker@scyld.com (Donald Becker)
Date: Thu Jul 25 17:17:01 2002
Subject: [realtek-bug] rtl8139 - another repeating error (??)
In-Reply-To: <004801c23419$96c82100$c40112ac@kromos.com>
Message-ID:
On Thu, 25 Jul 2002, Dan Miller wrote:
> The source code *does* still have the message, in
> static void rtl8129_tx_timeout(struct net_device *dev);
Yes, the message is there. It is an important check.
The false-trigger window was when the timer-based consistency check
triggered incorrectly after an interrupt was not immediately handled.
Any message from the current driver is reporting a real problem.
> The link partner is a Netgear FS108 Switch. I don't know whether the
> link beat is dropping, though webstone *does* put a heavy load on the
> system (both in amount of traffic and in number of TCP connections)
> ...
--
Donald Becker becker@scyld.com
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210 Second Generation Beowulf Clusters
Annapolis MD 21403 410-990-9993