Bizarre Transmission-induced network bug, driver crapping out maybe?

Chris Neary chris.neary at
Sun Feb 28 11:01:20 UTC 2010

Ok, wow, thanks for all the replies to my little retarded problem,
first of all. :)

Second, I did try changing the overall connection limit in
Transmission to <100 (I set it at 80 first). It seemed to be working,
until I woke up to the same problem this morning.

Tail'd /var/log/syslog and /var/log/messages but I was too late of course.

So I restarted the networking service and watched it happen again over
the course of a minute or two.

/var/log/syslog showed this:

Feb 28 10:52:02 empress kernel: [88632.816023] eth0: mii lpa=45e1
adv=01e1 exp=0001.
Feb 28 10:52:02 empress kernel: [88632.816031] eth0: link on 100 Mbps
Full Duplex mode.
Feb 28 10:52:03 empress kernel: [88633.465188] eth0: mii ext = 0000.
Feb 28 10:52:03 empress kernel: [88633.488028] eth0: mii lpa=45e1
adv=01e1 exp=0001.
Feb 28 10:52:03 empress kernel: [88633.488036] eth0: link on 100 Mbps
Full Duplex mode.

But nothing else related to eth0.

ifconfig displays:

eth0      Link encap:Ethernet  HWaddr 00:1b:b9:a7:c0:1d
          inet addr:  Bcast:  Mask:
          inet6 addr: fe80::21b:b9ff:fea7:c01d/64 Scope:Link
          RX packets:1577087 errors:36 dropped:0 overruns:0 frame:36
          TX packets:1475172 errors:0 dropped:64 overruns:0 carrier:0
          collisions:762 txqueuelen:1000
          RX bytes:1073393885 (1.0 GB)  TX bytes:845081642 (845.0 MB)
          Interrupt:19 Base address:0xdead

I'm not entirely sure what that means. My eyes/ears prick up over the
errors:36 though, but I've no idea what to do about that.

At this point if I ping the router or anything else I get Destination
Host Unreachable.

I don't think it's the router's fault, because the router stays
functional throughout, and I restart my local service to get it to
work again, without touching the router itself.

To answer the other questions the NIC is onboard sis190, as I said;
useless hardware! May buy a white-box NIC from Maplin tomorrow, and
try that.

I'll also try plugging direct to the net rather than via the router,
but I doubt it will change anything.

Cheers guys. :)

On 27 February 2010 14:21, Amedee Van Gasse <amedee-ubuntu at> wrote:
> On 27-02-10 14:30, Chan Chung Hang Christopher wrote:
>> Chan Chung Hang Christopher wrote:
>>>> The tell-tale signs that this has happened are there: All my torrents
>>>> are displaying 'Remaining time unknown, idle', and if I ping
>>>> Motherboard is onboard, SIS190. This never happened with my Acer
>>>> Aspire One via wireless, so I'm assuming its the driver/eth/board.
>>> realtek nic? Which version of Ubuntu? Hardy?
>> If you tail /var/log/syslog, you should see kernel messages regarding
>> the problem. One possible temporary solution would be to stop networking
>> and then start it least on Redhat/Fedora boxes. They would
>> unload the driver and reset everything.
> You should also tail the /var/log/syslog of your router, because at this
> moment it is not clear if the pc nic crashes, or the router. I suspect
> that it is the router, see my previous reply.
> I leave it as an exercise for the reader to tail any logfile of a remote
> device. You will at least need custom linux-based firmware for the router.
> --
> ubuntu-users mailing list
> ubuntu-users at
> Modify settings or unsubscribe at:

More information about the ubuntu-users mailing list