Re: My internet connection falls and only returns when I restart the computer.
On 09/18/2007 01:36 PM, Michael wrote:
> Hello everyone!
>
> I Installed Debian 4.0 (Etch) on my notebook Toshiba Satellite A105
> S2091 a couple of weeks ago and I've been facing this extremely annoying
> problem since then: my internet connection falls, for absolutely any
> apparent reason, and only returns after completely restarting the
> system. Nothing else works! I've already tried the internet service from
> somewhere else, restarting my modem, unplugging and replugging the
> wires, the GNOME applications, the `ifdown eth0' and `ifup eth0'
> commands on a shell and several combinations of these.
Perhaps '/etc/init.d/networking restart', but I'm no expert.
> After discussing this on the Brasilian users list, someone pointed out
> the possibility of a problem with the driver for my card. The output of
> `lspci' gives me, among several other lines,
>
> `
> 02:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL-8139/8139C/8139C+ (rev 10)
On this desktop, I also have this card... Ethernet controller: Realtek
Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
> ntbkmichael:/home/michael# lsmod
> Module Size Used by
> 8139cp 21920 0
> 8139too 25120 0
Yes, 8139too is the module used for this card, but I also have the
8139cp loaded somehow, so this is not the problem.
> Does anybody have a clue of what might be happening? The excerpt of the
> output of `grep eth0 /var/log/kern.log' referring to one of the many
> sessions in which I've eventually lost my connection was
>
> `
> Sep 16 15:57:16 ntbkmichael kernel: eth0: RealTek RTL8139 at 0xa000,
> 00:a0:d1:38:4f:b6, IRQ 201
> Sep 16 15:57:16 ntbkmichael kernel: eth0: Identified 8139 chip type
> 'RTL-8100B/8139D'
> Sep 16 15:57:16 ntbkmichael kernel: eth0: link up, 100Mbps, full-duplex,
> lpa 0x45E1
You are fine up to here; this is what mine looks like. I have nothing
following this line. "link up" of course says OK to here, connection
established.
What is NETDEV WATCHDOG? Something appears to interfere here AFTER your
link is up and running.
Searching for 'kernel: NETDEV WATCHDOG: eth0:' gives plenty of leads for
research if you don't get more help here.
> Sep 16 16:09:27 ntbkmichael kernel: NETDEV WATCHDOG: eth0: transmit
> timed out
> Sep 16 16:09:30 ntbkmichael kernel: eth0: Transmit timeout, status 0c
> 0005 c07f media 00.
> Sep 16 16:09:30 ntbkmichael kernel: eth0: Tx queue start entry 6562
> dirty entry 6558.
> Sep 16 16:09:30 ntbkmichael kernel: eth0: Tx descriptor 0 is 0008a042.
> Sep 16 16:09:30 ntbkmichael kernel: eth0: Tx descriptor 1 is 0008a042.
> Sep 16 16:09:30 ntbkmichael kernel: eth0: Tx descriptor 2 is 0008a042.
> (queue head)
> Sep 16 16:09:30 ntbkmichael kernel: eth0: Tx descriptor 3 is 0008a042.
> Sep 16 16:09:30 ntbkmichael kernel: eth0: link up, 100Mbps, full-duplex,
> lpa 0x45E1
> Sep 16 16:09:42 ntbkmichael kernel: NETDEV WATCHDOG: eth0: transmit
> timed out
> Sep 16 16:09:45 ntbkmichael kernel: eth0: Transmit timeout, status 0c
> 0005 c07f media 00.
> Sep 16 16:09:45 ntbkmichael kernel: eth0: Tx queue start entry 4 dirty
> entry 0.
> Sep 16 16:09:45 ntbkmichael kernel: eth0: Tx descriptor 0 is 0008a042.
> (queue head)
> Sep 16 16:09:45 ntbkmichael kernel: eth0: Tx descriptor 1 is 0008a04b.
> Sep 16 16:09:45 ntbkmichael kernel: eth0: Tx descriptor 2 is 0008a04b.
> Sep 16 16:09:45 ntbkmichael kernel: eth0: Tx descriptor 3 is 0008a042.
> Sep 16 16:09:45 ntbkmichael kernel: eth0: link up, 100Mbps, full-duplex,
> lpa 0x45E1
> Sep 16 16:09:57 ntbkmichael kernel: NETDEV WATCHDOG: eth0: transmit
> timed out
> Sep 16 16:10:00 ntbkmichael kernel: eth0: Transmit timeout, status 0c
> 0005 c07f media 00.
> Sep 16 16:10:00 ntbkmichael kernel: eth0: Tx queue start entry 4 dirty
> entry 0.
> Sep 16 16:10:00 ntbkmichael kernel: eth0: Tx descriptor 0 is 0008a04b.
> (queue head)
> Sep 16 16:10:00 ntbkmichael kernel: eth0: Tx descriptor 1 is 0008a04b.
> Sep 16 16:10:00 ntbkmichael kernel: eth0: Tx descriptor 2 is 0008a05d.
> Sep 16 16:10:00 ntbkmichael kernel: eth0: Tx descriptor 3 is 0008a05d.
> Sep 16 16:10:00 ntbkmichael kernel: eth0: link up, 100Mbps, full-duplex,
> lpa 0x45E1
> '
Keep us posted, and good luck!
Ralph Katz
Reply to: