Re: [expert] NEED HELP - kernel: eth0: Tx hung, 1191883 vs.1191882.
Had a sit where a guy did a 10kw lin-year base station 30 feet from my parents house... when the stereo was OFF you could still here him when he keyed up. (then again so did the FCC *grin*) Talk about a ghost in the machine. James On Wed, 2003-01-08 at 13:39, Todd Lyons wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Jim C wrote on Wed, Jan 08, 2003 at 01:32:00PM -0800 : > > Don't forget about the possibility of inductance. > > There might be a power source nearby that is getting onto your wires. > > Many years ago in the days of Dialup BBSs I used to get bumped of the > > internet by truckers on the freeway who were illegally boosting their > > signals. > > Since the FCC legal limit is 4 watts, it doesn't take much to get > illegal. But you don't usually see problems being caused to other > electronics devices until the power gets up over 100W. (Funny note, > truckers refer to them as a "Linear", pronounced by them as Lin-year, > obviously a cropping of the full name "linear amplifier".) Having said > that, it's common to see 1KW and higher Linears on long haul truckers' > rigs. > > Blue skies... Todd > - -- >MandrakeSoft USA http://www.mandrakesoft.com > Mandrake: An amalgam of good ideas from RedHat, Debian, and MandrakeSoft. > All in all, IMHO, an unbeatable combination. --Levi Ramsey on Cooker ML >Cooker Version mandrake-release-9.1-0.1mdk Kernel 2.4.20-2mdk > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.2.1 (GNU/Linux) > > iD8DBQE+HJqNlp7v05cW2woRAmYSAKCWUGdJ/1JNSVCfIUU183QC2s3maACdHXjY > yIDErhlvJFlfy3pXNje2DY4= > =R49Q > -END PGP SIGNATURE- > > > __ > > Want to buy your Pack or Services from MandrakeSoft? > Go to http://www.mandrakestore.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] NEED HELP - kernel: eth0: Tx hung, 1191883 vs.1191882.
On Wednesday 08 January 2003 10:21 am, David Rankin wrote: > Pierre Fortin wrote: > > On Tue, 7 Jan 2003 23:33:51 -0600 "David Rankin" > > > > <[EMAIL PROTECTED]> wrote: > > > I have been struggling with a weird message lately that hasn't appeared > > > over the past 2 years until the past few weeks. I don't have any clue > > > as to what this is actually telling me, but I would suspect that it may > > > be the initial gasps of a dying LNE100TX network card (tulip driver). > > > It may only show up once or twice every week. However, with my very > > > limited kernel error message understanding, I'm at a loss. So experts > > > -- Chime in! > > > > > > Setup: > > > > > > LM 7.2 Odyssey (2.2.19 kernel) > > > Abit Kt7 mb > > > AMD T-bird 800 > > > Linksys LNE100TX > > > (No hardware changes since Jan, 2001) > > > > Does the 'no changes' comment also apply to all the connected systems in > > the office? Is anyone using a new app on the non-Linux boxes? Was there > > a storm just before this problem started? (One of my LinkSys ports was > > zapped by lightning induction -- the connected box was not affected) > > Well, this is interesting because there was one hell of a lightning storm > several days before this problem appeared. The only reason I don't think > this correlates is because the errors didn't appear until a few days after. > > What about moisture around the CAT5 cables. Our office is an older > structure that sits on pier and beam with the CAT5 run underneath. After > the storm, it is possible the CAT5 was in a very moist environment. The > CAT5 insulation should be good on all the cables. Has anyone heard of > moisture around cables causing this type of problem? > Would it be possible to take a new cable and run it on the floor and see if the problem goes away for a day? Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] NEED HELP - kernel: eth0: Tx hung, 1191883 vs. 1191882.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim C wrote on Wed, Jan 08, 2003 at 01:32:00PM -0800 : > Don't forget about the possibility of inductance. > There might be a power source nearby that is getting onto your wires. > Many years ago in the days of Dialup BBSs I used to get bumped of the > internet by truckers on the freeway who were illegally boosting their > signals. Since the FCC legal limit is 4 watts, it doesn't take much to get illegal. But you don't usually see problems being caused to other electronics devices until the power gets up over 100W. (Funny note, truckers refer to them as a "Linear", pronounced by them as Lin-year, obviously a cropping of the full name "linear amplifier".) Having said that, it's common to see 1KW and higher Linears on long haul truckers' rigs. Blue skies... Todd - -- MandrakeSoft USA http://www.mandrakesoft.com Mandrake: An amalgam of good ideas from RedHat, Debian, and MandrakeSoft. All in all, IMHO, an unbeatable combination. --Levi Ramsey on Cooker ML Cooker Version mandrake-release-9.1-0.1mdk Kernel 2.4.20-2mdk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+HJqNlp7v05cW2woRAmYSAKCWUGdJ/1JNSVCfIUU183QC2s3maACdHXjY yIDErhlvJFlfy3pXNje2DY4= =R49Q -END PGP SIGNATURE- Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] NEED HELP - kernel: eth0: Tx hung, 1191883 vs. 1191882.
Don't forget about the possibility of inductance. There might be a power source nearby that is getting onto your wires. Many years ago in the days of Dialup BBSs I used to get bumped of the internet by truckers on the freeway who were illegally boosting their signals. et wrote: On Wednesday 08 January 2003 08:49 am, Lorne wrote: On Wednesday 08 January 2003 06:34 am, et wrote: no warrenty on this, but with everything running so well for so long,,, consider the posible cables may have gotten bumped or steped on in such a way it mat have pulled a little loose? have you reseated the cables? I don't think it would be cables, although that would be a common problem. the reason I say that is because if it was a cable the driver would still load with no problems. This seems to be hardware problems. I wonder if you have added any hardware to cause an IRQ conflict that is sporatic? If NOTHING has changed then I'd change the nic and see what happens. from my reading, the driver (Module) is loaded fine, it is an intermittant failure in a packet transmission. the first thing _I_ personally would look for, since this is right after christmas, is did you get an new flourecent or Halogen light/Lamp and set it near where the cable runs? On Wednesday 08 January 2003 12:33 am, David Rankin wrote: I have been struggling with a weird message lately that hasn't appeared over the past 2 years until the past few weeks. I don't have any clue as to what this is actually telling me, but I would suspect that it may be the initial gasps of a dying LNE100TX network card (tulip driver). It may only show up once or twice every week. However, with my very limited kernel error message understanding, I'm at a loss. So experts -- Chime in! Setup: LM 7.2 Odyssey (2.2.19 kernel) Abit Kt7 mb AMD T-bird 800 Linksys LNE100TX (No hardware changes since Jan, 2001) Network: server -> 8 port C-net hub [7 out to LAN 1 to] -> 4 port Linksys cable/dsl router [1 LAN connection] -> (the rest of the world/internet) No problems for over 580 days. Since 12/26/02 I have received the following message with varying frequency. It really hung on the 12/26, but after that I only see the message once maybe twice a day or week? Jan 3 11:28:22 Nemesis kernel: eth0: Tx hung, 1191883 vs. 1191882. Jan 3 11:28:22 Nemesis kernel: eth0: PNIC2 transmit timed out, status e400, CSR6/7 0100 / ebff CSR12 40a1d0cc, resetting... OK, this is Jan 7 and I haven't had the message since the 3rd, so: What in the heck does this error mean? Google says that it may be a tulip driver error, but that is no explaination as to why I would go 500+ days without the error and then have it magically (or a a result of witchcraft) appear? Does it smell like a hardware problem? When it occurs, I have noticed that my C-net 8 port hub acts flakey. After I disconnect all the clients, reset the modem, reset the router, reset the hub -- everything seems OK. So what gives? (I generally do a /init.d/network restart just to be on the safe side) Which resets without any errors. My real question is what in the hell is an: eth0: Tx hung message mean? What does the eth0: PNIC2 message mean? Docos and info is sparse on this message. So, has anyone else got a clue as to what I'm dealing with? As always, any wisdom would be greatly appreciated. Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] NEED HELP - kernel: eth0: Tx hung, 1191883 vs.1191882.
On Wednesday 08 January 2003 01:03 pm, Pierre Fortin wrote: > On Wed, 08 Jan 2003 11:21:25 -0600 David Rankin <[EMAIL PROTECTED]> > > wrote: > > Pierre Fortin wrote: > > > On Tue, 7 Jan 2003 23:33:51 -0600 "David Rankin" > > > > > > <[EMAIL PROTECTED]> wrote: > > > > I have been struggling with a weird message lately that hasn't > > > > appeared over the past 2 years until the past few weeks. I don't > > > > have any clue as to what this is actually telling me, but I would > > > > suspect that it may be the initial gasps of a dying LNE100TX network > > > > card (tulip driver). It may only show up once or twice every week. > > > > However, with my very limited kernel error message understanding, > > > > I'm at a loss. So experts -- Chime in! > > > > > > > > Setup: > > > > > > > > LM 7.2 Odyssey (2.2.19 kernel) > > > > Abit Kt7 mb > > > > AMD T-bird 800 > > > > Linksys LNE100TX > > > > (No hardware changes since Jan, 2001) > > > > > > Does the 'no changes' comment also apply to all the connected systems > > > in the office? Is anyone using a new app on the non-Linux boxes? Was > > > there a storm just before this problem started? (One of my LinkSys > > > ports was zapped by lightning induction -- the connected box was not > > > affected) > > > > Well, this is interesting because there was one hell of a lightning > > storm several days before this problem appeared. The only reason I don't > > think this correlates is because the errors didn't appear until a few > > days after. > > > > What about moisture around the CAT5 cables. Our office is an older > > structure that sits on pier and beam with the CAT5 run underneath. After > > the storm, it is possible the CAT5 was in a very moist environment. The > > CAT5 insulation should be good on all the cables. Has anyone heard of > > moisture around cables causing this type of problem? > > I experienced those Texas storms for a few years, so I know what you > mean... :^) > > Moisture would change resistance/capacitance characteristics of the cable; > especially if rodents got at the cable... > > While the cable is wet, the real problems could show up as it started to > dry (especially if sitting on the ground) since the ratio of > minerals:water would go up as the cable dried. Speculation; but a quick > examination of the cables would eliminate/confirm that possibility. > > Similar problems can happen if the cable was punctured by a staple during > installation, and the staple is rusting inside the cable. Yep, and from accumulated effects of age and temp change and gamma radiation drying out the insulation. you gots to have _GooD_ cables. > HTH, > Pierre > > > > > Network: > > > > > > > > server -> 8 port C-net hub [7 out to LAN 1 to] -> 4 port Linksys > > > > cable/dsl router [1 LAN connection] -> (the rest of the > > > > world/internet) > > > > > > > > > > > > No problems for over 580 days. Since 12/26/02 I have received the > > > > following message with varying frequency. It really hung on the > > > > 12/26, but after that I only see the message once maybe twice a day > > > > or week? > > > > > > > > Jan 3 11:28:22 Nemesis kernel: eth0: Tx hung, 1191883 vs. 1191882. > > > > Jan 3 11:28:22 Nemesis kernel: eth0: PNIC2 transmit timed out, > > > > status e400, CSR6/7 0100 / ebff > > > > CSR12 40a1d0cc, resetting... > > > > > > > > OK, this is Jan 7 and I haven't had the message since the 3rd, so: > > > > > > > > What in the heck does this error mean? Google says that it may be a > > > > tulip driver error, but that is no explaination as to why I would go > > > > 500+ days without the error and then have it magically (or a a > > > > result of witchcraft) appear? Does it smell like a hardware problem? > > > > When it occurs, I have noticed that my C-net 8 port hub acts flakey. > > > > After I disconnect all the clients, reset the modem, reset the > > > > router, reset the hub -- everything seems OK. So what gives? (I > > > > generally do a/init.d/network restart just to be on the safe > > > > side) Which resets without any errors. > > > > > > > > My real question is what in the hell is an: eth0: Tx hung message > > > > mean? What does the eth0: PNIC2 message mean? Docos and info is > > > > sparse on this message. So, has anyone else got a clue as to what > > > > I'm dealing with? > > > > > > This is gonna require the 7.2 sources (which I no longer have) and a > > > read of the code -- that was the only source of docs that helped when > > > I had eepro10 problems on 7.2... > > > > > > > As always, any wisdom would be greatly appreciated. > > > > > > Running ethereal won't show such a low level problem; but it might > > > provide a clue if a bug is triggered by something on the LAN > > > condisdering you are using a hub... > > > > > > HTH, > > > Pierre > > > > > > > -- > > > > David C. Rankin, J.D., P.E. > > > > Rankin * Bertin, PLLC > > > > 510 Ochiltree Street > > > > Nacogdoches, Texas 75961 > > > > (936) 715-9333 > > > > > > --
Re: [expert] NEED HELP - kernel: eth0: Tx hung, 1191883 vs.1191882.
On Wed, 08 Jan 2003 11:21:25 -0600 David Rankin <[EMAIL PROTECTED]> wrote: > > > Pierre Fortin wrote: > > > On Tue, 7 Jan 2003 23:33:51 -0600 "David Rankin" > > <[EMAIL PROTECTED]> wrote: > > > > > > > > I have been struggling with a weird message lately that hasn't > > > appeared over the past 2 years until the past few weeks. I don't > > > have any clue as to what this is actually telling me, but I would > > > suspect that it may be the initial gasps of a dying LNE100TX network > > > card (tulip driver). It may only show up once or twice every week. > > > However, with my very limited kernel error message understanding, > > > I'm at a loss. So experts -- Chime in! > > > > > > Setup: > > > > > > LM 7.2 Odyssey (2.2.19 kernel) > > > Abit Kt7 mb > > > AMD T-bird 800 > > > Linksys LNE100TX > > > (No hardware changes since Jan, 2001) > > > > Does the 'no changes' comment also apply to all the connected systems > > in the office? Is anyone using a new app on the non-Linux boxes? Was > > there a storm just before this problem started? (One of my LinkSys > > ports was zapped by lightning induction -- the connected box was not > > affected) > > > > Well, this is interesting because there was one hell of a lightning > storm several days before this problem appeared. The only reason I don't > think this correlates is because the errors didn't appear until a few > days after. > > What about moisture around the CAT5 cables. Our office is an older > structure that sits on pier and beam with the CAT5 run underneath. After > the storm, it is possible the CAT5 was in a very moist environment. The > CAT5 insulation should be good on all the cables. Has anyone heard of > moisture around cables causing this type of problem? I experienced those Texas storms for a few years, so I know what you mean... :^) Moisture would change resistance/capacitance characteristics of the cable; especially if rodents got at the cable... While the cable is wet, the real problems could show up as it started to dry (especially if sitting on the ground) since the ratio of minerals:water would go up as the cable dried. Speculation; but a quick examination of the cables would eliminate/confirm that possibility. Similar problems can happen if the cable was punctured by a staple during installation, and the staple is rusting inside the cable. HTH, Pierre > > > > > Network: > > > > > > server -> 8 port C-net hub [7 out to LAN 1 to] -> 4 port Linksys > > > cable/dsl router [1 LAN connection] -> (the rest of the > > > world/internet) > > > > > > > > > No problems for over 580 days. Since 12/26/02 I have received the > > > following message with varying frequency. It really hung on the > > > 12/26, but after that I only see the message once maybe twice a day > > > or week? > > > > > > Jan 3 11:28:22 Nemesis kernel: eth0: Tx hung, 1191883 vs. 1191882. > > > Jan 3 11:28:22 Nemesis kernel: eth0: PNIC2 transmit timed out, > > > status e400, CSR6/7 0100 / ebff > > > CSR12 40a1d0cc, resetting... > > > > > > OK, this is Jan 7 and I haven't had the message since the 3rd, so: > > > > > > What in the heck does this error mean? Google says that it may be a > > > tulip driver error, but that is no explaination as to why I would go > > > 500+ days without the error and then have it magically (or a a > > > result of witchcraft) appear? Does it smell like a hardware problem? > > > When it occurs, I have noticed that my C-net 8 port hub acts flakey. > > > After I disconnect all the clients, reset the modem, reset the > > > router, reset the hub -- everything seems OK. So what gives? (I > > > generally do a/init.d/network restart just to be on the safe > > > side) Which resets without any errors. > > > > > > My real question is what in the hell is an: eth0: Tx hung message > > > mean? What does the eth0: PNIC2 message mean? Docos and info is > > > sparse on this message. So, has anyone else got a clue as to what > > > I'm dealing with? > > > > This is gonna require the 7.2 sources (which I no longer have) and a > > read of the code -- that was the only source of docs that helped when > > I had eepro10 problems on 7.2... > > > > > As always, any wisdom would be greatly appreciated. > > > > Running ethereal won't show such a low level problem; but it might > > provide a clue if a bug is triggered by something on the LAN > > condisdering you are using a hub... > > > > HTH, > > Pierre > > > > > -- > > > David C. Rankin, J.D., P.E. > > > Rankin * Bertin, PLLC > > > 510 Ochiltree Street > > > Nacogdoches, Texas 75961 > > > (936) 715-9333 > > > > > > > > > > > > > --- > > - > > Want to buy your Pack or Services from MandrakeSoft? > > Go to http://www.mandrakestore.com > > -- > David C. Rankin, J.D., P.E. > RANKIN * BERTIN, PLLC > 510 Ochiltree Street > Nacogdoches, Texas 75961 > (936) 715-9333 > (936) 715-9339 fax > > > > Want to buy your Pack or Services from Mandrak
Re: [expert] NEED HELP - kernel: eth0: Tx hung, 1191883 vs.1191882.
Pierre Fortin wrote: > On Tue, 7 Jan 2003 23:33:51 -0600 "David Rankin" > <[EMAIL PROTECTED]> wrote: > > > > > I have been struggling with a weird message lately that hasn't appeared > > over the past 2 years until the past few weeks. I don't have any clue as > > to what this is actually telling me, but I would suspect that it may be > > the initial gasps of a dying LNE100TX network card (tulip driver). It > > may only show up once or twice every week. However, with my very limited > > kernel error message understanding, I'm at a loss. So experts -- Chime > > in! > > > > Setup: > > > > LM 7.2 Odyssey (2.2.19 kernel) > > Abit Kt7 mb > > AMD T-bird 800 > > Linksys LNE100TX > > (No hardware changes since Jan, 2001) > > Does the 'no changes' comment also apply to all the connected systems in > the office? Is anyone using a new app on the non-Linux boxes? Was there > a storm just before this problem started? (One of my LinkSys ports was > zapped by lightning induction -- the connected box was not affected) > Well, this is interesting because there was one hell of a lightning storm several days before this problem appeared. The only reason I don't think this correlates is because the errors didn't appear until a few days after. What about moisture around the CAT5 cables. Our office is an older structure that sits on pier and beam with the CAT5 run underneath. After the storm, it is possible the CAT5 was in a very moist environment. The CAT5 insulation should be good on all the cables. Has anyone heard of moisture around cables causing this type of problem? > > > Network: > > > > server -> 8 port C-net hub [7 out to LAN 1 to] -> 4 port Linksys > > cable/dsl router [1 LAN connection] -> (the rest of the world/internet) > > > > > > No problems for over 580 days. Since 12/26/02 I have received the > > following message with varying frequency. It really hung on the 12/26, > > but after that I only see the message once maybe twice a day or week? > > > > Jan 3 11:28:22 Nemesis kernel: eth0: Tx hung, 1191883 vs. 1191882. > > Jan 3 11:28:22 Nemesis kernel: eth0: PNIC2 transmit timed out, status > > e400, CSR6/7 0100 / ebff > > CSR12 40a1d0cc, resetting... > > > > OK, this is Jan 7 and I haven't had the message since the 3rd, so: > > > > What in the heck does this error mean? Google says that it may be a > > tulip driver error, but that is no explaination as to why I would go > > 500+ days without the error and then have it magically (or a a result of > > witchcraft) appear? Does it smell like a hardware problem? When it > > occurs, I have noticed that my C-net 8 port hub acts flakey. After I > > disconnect all the clients, reset the modem, reset the router, reset the > > hub -- everything seems OK. So what gives? (I generally do a > > /init.d/network restart just to be on the safe side) Which resets > > without any errors. > > > > My real question is what in the hell is an: eth0: Tx hung message mean? > > What does the eth0: PNIC2 message mean? Docos and info is sparse on this > > message. So, has anyone else got a clue as to what I'm dealing with? > > This is gonna require the 7.2 sources (which I no longer have) and a read > of the code -- that was the only source of docs that helped when I had > eepro10 problems on 7.2... > > > As always, any wisdom would be greatly appreciated. > > Running ethereal won't show such a low level problem; but it might provide > a clue if a bug is triggered by something on the LAN condisdering you are > using a hub... > > HTH, > Pierre > > > -- > > David C. Rankin, J.D., P.E. > > Rankin * Bertin, PLLC > > 510 Ochiltree Street > > Nacogdoches, Texas 75961 > > (936) 715-9333 > > > > > > > > > Want to buy your Pack or Services from MandrakeSoft? > Go to http://www.mandrakestore.com -- David C. Rankin, J.D., P.E. RANKIN * BERTIN, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] NEED HELP - kernel: eth0: Tx hung, 1191883 vs.1191882.
On Tue, 7 Jan 2003 23:33:51 -0600 "David Rankin" <[EMAIL PROTECTED]> wrote: > > I have been struggling with a weird message lately that hasn't appeared > over the past 2 years until the past few weeks. I don't have any clue as > to what this is actually telling me, but I would suspect that it may be > the initial gasps of a dying LNE100TX network card (tulip driver). It > may only show up once or twice every week. However, with my very limited > kernel error message understanding, I'm at a loss. So experts -- Chime > in! > > Setup: > > LM 7.2 Odyssey (2.2.19 kernel) > Abit Kt7 mb > AMD T-bird 800 > Linksys LNE100TX > (No hardware changes since Jan, 2001) Does the 'no changes' comment also apply to all the connected systems in the office? Is anyone using a new app on the non-Linux boxes? Was there a storm just before this problem started? (One of my LinkSys ports was zapped by lightning induction -- the connected box was not affected) > Network: > > server -> 8 port C-net hub [7 out to LAN 1 to] -> 4 port Linksys > cable/dsl router [1 LAN connection] -> (the rest of the world/internet) > > > No problems for over 580 days. Since 12/26/02 I have received the > following message with varying frequency. It really hung on the 12/26, > but after that I only see the message once maybe twice a day or week? > > Jan 3 11:28:22 Nemesis kernel: eth0: Tx hung, 1191883 vs. 1191882. > Jan 3 11:28:22 Nemesis kernel: eth0: PNIC2 transmit timed out, status > e400, CSR6/7 0100 / ebff > CSR12 40a1d0cc, resetting... > > OK, this is Jan 7 and I haven't had the message since the 3rd, so: > > What in the heck does this error mean? Google says that it may be a > tulip driver error, but that is no explaination as to why I would go > 500+ days without the error and then have it magically (or a a result of > witchcraft) appear? Does it smell like a hardware problem? When it > occurs, I have noticed that my C-net 8 port hub acts flakey. After I > disconnect all the clients, reset the modem, reset the router, reset the > hub -- everything seems OK. So what gives? (I generally do a > /init.d/network restart just to be on the safe side) Which resets > without any errors. > > My real question is what in the hell is an: eth0: Tx hung message mean? > What does the eth0: PNIC2 message mean? Docos and info is sparse on this > message. So, has anyone else got a clue as to what I'm dealing with? This is gonna require the 7.2 sources (which I no longer have) and a read of the code -- that was the only source of docs that helped when I had eepro10 problems on 7.2... > As always, any wisdom would be greatly appreciated. Running ethereal won't show such a low level problem; but it might provide a clue if a bug is triggered by something on the LAN condisdering you are using a hub... HTH, Pierre > -- > David C. Rankin, J.D., P.E. > Rankin * Bertin, PLLC > 510 Ochiltree Street > Nacogdoches, Texas 75961 > (936) 715-9333 > > > Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] NEED HELP - kernel: eth0: Tx hung, 1191883 vs. 1191882.
On Wednesday 08 January 2003 08:49 am, Lorne wrote: > On Wednesday 08 January 2003 06:34 am, et wrote: > > no warrenty on this, but with everything running so well for so long,,, > > consider the posible cables may have gotten bumped or steped on in such a > > way it mat have pulled a little loose? have you reseated the cables? > > I don't think it would be cables, although that would be a common problem. > the reason I say that is because if it was a cable the driver would still > load with no problems. This seems to be hardware problems. I wonder if you > have added any hardware to cause an IRQ conflict that is sporatic? If > NOTHING has changed then I'd change the nic and see what happens. from my reading, the driver (Module) is loaded fine, it is an intermittant failure in a packet transmission. the first thing _I_ personally would look for, since this is right after christmas, is did you get an new flourecent or Halogen light/Lamp and set it near where the cable runs? > > On Wednesday 08 January 2003 12:33 am, David Rankin wrote: > > > I have been struggling with a weird message lately that hasn't appeared > > > over the past 2 years until the past few weeks. I don't have any clue > > > as to what this is actually telling me, but I would suspect that it may > > > be the initial gasps of a dying LNE100TX network card (tulip driver). > > > It may only show up once or twice every week. However, with my very > > > limited kernel error message understanding, I'm at a loss. So experts > > > -- Chime in! > > > > > > Setup: > > > > > > LM 7.2 Odyssey (2.2.19 kernel) > > > Abit Kt7 mb > > > AMD T-bird 800 > > > Linksys LNE100TX > > > (No hardware changes since Jan, 2001) > > > > > > Network: > > > > > > server -> 8 port C-net hub [7 out to LAN 1 to] -> 4 port Linksys > > > cable/dsl router [1 LAN connection] -> (the rest of the world/internet) > > > > > > > > > No problems for over 580 days. Since 12/26/02 I have received the > > > following message with varying frequency. It really hung on the 12/26, > > > but after that I only see the message once maybe twice a day or week? > > > > > > Jan 3 11:28:22 Nemesis kernel: eth0: Tx hung, 1191883 vs. 1191882. > > > Jan 3 11:28:22 Nemesis kernel: eth0: PNIC2 transmit timed out, status > > > e400, CSR6/7 0100 / ebff > > > CSR12 40a1d0cc, resetting... > > > > > > OK, this is Jan 7 and I haven't had the message since the 3rd, so: > > > > > > What in the heck does this error mean? Google says that it may be a > > > tulip driver error, but that is no explaination as to why I would go > > > 500+ days without the error and then have it magically (or a a result > > > of witchcraft) appear? Does it smell like a hardware problem? When it > > > occurs, I have noticed that my C-net 8 port hub acts flakey. After I > > > disconnect all the clients, reset the modem, reset the router, reset > > > the hub -- everything seems OK. So what gives? (I generally do a > > > /init.d/network restart just to be on the safe side) Which resets > > > without any errors. > > > > > > My real question is what in the hell is an: eth0: Tx hung message mean? > > > What does the eth0: PNIC2 message mean? Docos and info is sparse on > > > this message. So, has anyone else got a clue as to what I'm dealing > > > with? > > > > > > As always, any wisdom would be greatly appreciated. Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] NEED HELP - kernel: eth0: Tx hung, 1191883 vs. 1191882.
On Wednesday 08 January 2003 06:34 am, et wrote: > no warrenty on this, but with everything running so well for so long,,, > consider the posible cables may have gotten bumped or steped on in such a > way it mat have pulled a little loose? have you reseated the cables? > I don't think it would be cables, although that would be a common problem. the reason I say that is because if it was a cable the driver would still load with no problems. This seems to be hardware problems. I wonder if you have added any hardware to cause an IRQ conflict that is sporatic? If NOTHING has changed then I'd change the nic and see what happens. > On Wednesday 08 January 2003 12:33 am, David Rankin wrote: > > I have been struggling with a weird message lately that hasn't appeared > > over the past 2 years until the past few weeks. I don't have any clue as > > to what this is actually telling me, but I would suspect that it may be > > the initial gasps of a dying LNE100TX network card (tulip driver). It may > > only show up once or twice every week. However, with my very limited > > kernel error message understanding, I'm at a loss. So experts -- Chime > > in! > > > > Setup: > > > > LM 7.2 Odyssey (2.2.19 kernel) > > Abit Kt7 mb > > AMD T-bird 800 > > Linksys LNE100TX > > (No hardware changes since Jan, 2001) > > > > Network: > > > > server -> 8 port C-net hub [7 out to LAN 1 to] -> 4 port Linksys > > cable/dsl router [1 LAN connection] -> (the rest of the world/internet) > > > > > > No problems for over 580 days. Since 12/26/02 I have received the > > following message with varying frequency. It really hung on the 12/26, > > but after that I only see the message once maybe twice a day or week? > > > > Jan 3 11:28:22 Nemesis kernel: eth0: Tx hung, 1191883 vs. 1191882. > > Jan 3 11:28:22 Nemesis kernel: eth0: PNIC2 transmit timed out, status > > e400, CSR6/7 0100 / ebff > > CSR12 40a1d0cc, resetting... > > > > OK, this is Jan 7 and I haven't had the message since the 3rd, so: > > > > What in the heck does this error mean? Google says that it may be a tulip > > driver error, but that is no explaination as to why I would go 500+ days > > without the error and then have it magically (or a a result of > > witchcraft) appear? Does it smell like a hardware problem? When it > > occurs, I have noticed that my C-net 8 port hub acts flakey. After I > > disconnect all the clients, reset the modem, reset the router, reset the > > hub -- everything seems OK. So what gives? (I generally do a > > /init.d/network restart just to be on the safe side) Which resets > > without any errors. > > > > My real question is what in the hell is an: eth0: Tx hung message mean? > > What does the eth0: PNIC2 message mean? Docos and info is sparse on this > > message. So, has anyone else got a clue as to what I'm dealing with? > > > > As always, any wisdom would be greatly appreciated. Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
