This bug report was marked as Incomplete and has not had any updated
comments for quite some time. As a result this bug is being closed.
Please reopen if this is still an issue in the current Ubuntu release
http://www.ubuntu.com/getubuntu/download . Also, please be sure to
provide any requested in
The bug was fixed in the .30 or maybe .31-version of the et131x-driver
in the linux kernel. Another bug is still there though which causes the
module to crash on high network loads (around 100 mbit/sec) which forces
the user to reload the kernel module to make the wired network respond
again. I hav
Hi Sarek,
This bug was reported a while ago and there hasn't been any activity in
it recently. We were wondering if this is still an issue? Can you try
with the latest development release of Ubuntu? ISO CD images are
available from http://cdimage.ubuntu.com/releases/lucid.
If it remains an issue
laptop mode with battery, success.
I can't confirm suspending since my /home is mounted on SD-card and
tifm_sd doesn't work yet with suspend. Going to google that up next.
** Attachment added: "Powertop -d (LG T1 with et131x running on battery)"
http://launchpadlibrarian.net/33104445/powertop-
Karmic Koala Alpha 3: et131x module is fixed.
Only 1 interrupt per second by et131x_error_timer_handler.
Added it via module-assistant.
I had problems previously with Ubuntu 7.10 onwards. Tested unsuccesfully
et131x-open, et131x.sf.net source, manual timer tuning as instructed
around bugs.launcp
I too can confirm this on a LG R200 laptop with the same ethernet
controller as mentioned above. Getting 250.2 wakeups / sec both with the
cable in and out with the latest jaunty kernel in the repositories
(2.6.28-12-generic). The same thing off course goes with the vanilla
jaunty kernel (28-11-som
Just updated to jaunty. I have an LG A1. I have the same problem.
uname -a outrput:
Linux wasp 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686
GNU/Linux
dmesg output after 'modprobe et13
Seems like the crash is not as reproducible as I thought, in my
experiments it just occured the one time I posted...
The high cpu usage still persists after my update to jaunty.
I am now running:
Linux enterprise 2.6.28-4-generic #8-Ubuntu SMP Mon Jan 5 22:35:11 UTC 2009
x86_64 GNU/Linux
--
hi
I have rebooted now. This is the powertop output:
PowerTOP version 1.10 (C) 2007 Intel Corporation
CnAvg residency P-states (frequencies)
C0 (cpu running)(78.1%) 1.80 Ghz 0.0%
polling 0.0ms ( 0.0%) 1.60 Ghz 0.0%
C1
